Performance monitoring systems and methods

ABSTRACT

We have disclosed systems and methods for portable performance monitoring of an individual during a physical activity. The systems and methods may include an input device configured to receive position data. The systems and methods may also include a processor configured to determine location information for the fitness activity based on the position data. The systems and methods may also include a memory operatively coupled to the processor and storing computer readable instructions that, when executed by the processor, cause the system to determine weather information based on the location information, and to determine athletic performance information. The systems and methods may also include a display screen configured to display the weather information and the athletic performance information to the individual.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.14/536,288, filed Nov. 7, 2014, which is a continuation of U.S.application Ser. No. 13,793,965, filed Mar. 11, 2013, which is acontinuation of U.S. application Ser. No. 13/789,266, filed Mar. 7,2013, which is a continuation of U.S. application Ser. No. 12/617,871,filed Nov. 13, 2009, which is a divisional of U.S. application Ser. No.10/645,713, filed Aug. 20, 2003, which is a continuation ofInternational App. No. PCT/US02/04947, filed Feb. 20, 2002, which claimsthe benefit of U.S. Provisional App. No. 60/270,400, filed Feb. 20,2001. The contents of each of these applications are expresslyincorporated herein by reference thereto in their entireties.

BACKGROUND OF THE INVENTION

Field of Invention

Our invention relates to modular personal network systems and methods.In particular this invention relates to wireless networks of individualcomponents that can be easily added to or removed from the network tochange its functions, and in which the individual components are worn,carried, or used on or about the person of the user.

Background Art

A number of individual portable personal devices are available today.Such personal devices provide specific functions to a person, in anumber of different fields of use. For example, there are mobile phones,personal digital assistants, medical monitoring devices, personalentertainment systems, and athletic monitoring systems. These and otherportable electronic devices have significantly improved the convenienceof many activities.

However, each of these functions is provided individually. None of theseindividual devices can combine with any of the other devices to provideimproved functions. If a user wishes to upgrade the capabilities of anyof these devices, a new, expensive device must be purchased and the olddevice discarded.

What is needed is a system in which individual portable device modulescan be combined in a multitude of ways to provide an infinite variety offunctions. A portable system is needed in which new functions can beadded by simply adding or replacing a single component. A portablesystem is needed in which the functions can be modified simply bydownloading new software or other parameters. A system is needed inwhich functions in different fields of use can be easily combined. And asystem is needed in which the economies of scale and scope of buildingdevices across multiple fields of use can be used to benefit users ofdevices in all of the fields of use.

Wireless communication protocols have been defined. Bluetooth and IEEE802.15 are two examples of protocols that may be used with personalportable devices. What is needed is a system that provides theadvantages of a modular personal network, and that uses a standardwireless communication protocol such as one of these.

U.S. Pat. No. 6,047,301 (2000) and U.S. Pat. No. 6,336,126 (2002) bothto Bjorklund, et al., disclose a wearable computer that communicateswith a display device using an optical link, and with a local areanetwork using a radio communications link. However, the system describedis not modular, nor is it extensible.

U.S. Pat. No. 6,324,053 (2001) to Kamijo discloses a wearable dataprocessing system. However, this system depends on a network of wiringstitched into the clothing of the user.

U.S. Pat. No. 6,108,197 (2000) to Janik discloses a flexible wearablecomputer. However, this disclosure does not envision the neededextensibility.

U.S. Pat. No. 5,781,913 (1998) to Felsenstein, et al., discloses awearable hypermedium system. It is designed to allow a user to access alarge amount of electronic information using a hands-free system, butdoes not include provisions for extending to other unanticipated uses.

A personal area network has been disclosed. For example, U.S. Pat. No.6,331,972 (2001) to Harris, et al., discloses a circuit and method forpersonalizing an electronic device through a personal area network. U.S.Pat. No. 6,314,091 (2001) to LaRowe, Jr., et al., discloses a wirelesspersonal area network with a plurality of peripheral devices, wherein ahub device provides attachment and detachment of peripheral devices.U.S. Pat. No. 6,128,290 (2000) to Carvey discloses a personal datanetwork that uses low duty cycle pulsed radio frequency energy tocommunicate and provide synchronization. U.S. Pat. No. 5,909,183 (1999)to Borgstahl, et al., discloses a method for programming an appliance bya controller in a personal area network. U.S. Pat. No. 5,898,831 (1999)to Hall, et al., discloses a method for including an appliance in apersonal area network and programming security criteria. However, noneof these systems provides the needed flexibility of our modular personalnetwork (MPN). For example, each of them requires a controller to be oneof the devices in the personal area network. These systems do notanticipate the needed methods for downloading data to a personal areanetwork from a personal computer or other system, nor for retrievingdata from a personal area network to a personal computer or othersystem. And the wide variety of components, configurations, and uses hasnot been anticipated.

Users need more flexibility in display devices, such as how they areworn so that they may be easily viewed during different activities.Users need display devices that can be easily modified in their positionand orientation. Users need a variety of mounting options for individualcomponents in an MPN. Users need an audio device that can be easily wornduring various activities, that can be heard during activities withambient noise, and that won't disturb other nearby people. Users need asystem that provides multiple types of audio output in an intelligentfashion. Users need a variety of input devices for different types ofactivities, and which can be easily accessed during those activities.

Users need to be able to reuse the same components for multiplepurposes. These purposes may include time keeping. Users need a networkthat allows communication with other individuals, who may or may nothave their own MPNs. Users need a network that provides entertainmentfeatures, including playing music, playing games, and capturing audioand video. Users need a portable system that combines personalorganization functions with other functions. Users need a mobile journalsystem that can be customized for different types of uses, such astravel, athletics, healthcare, or other purposes. Users need a systemthat provides guidance features, and combines them with other features,such as audio and video annotations, collection of personal data, andathletic workouts.

Users need a system that can provide a variety of athletic functions,such as downloading workout control parameters as well as uploadingresults of a workout. Users need a system that can interface withexercise equipment, bicycles, and other personal equipment. They need asystem that collects performance data, detects and corrects errors inthe collected data, and estimates secondary data, based on the collectedprimary data. Athletes need a mobile system to measure cadence andstride length. Some athletes need reminders to consume water, sodium,and food. Swimmers need a system to measure and log lap-swimmingworkouts. Runners and other athletes need a mobile system to provideform feedback. Athletes need a system that can work with another systemto provide a competition between multiple athletes.

Physical therapist, doctors, and other healthcare professionals need asystem that can provide a variety of functions, such as measuring usercapabilities, monitoring changes, keeping a medical journal, measuringmetabolic parameters, detecting medical problems, providing treatments,and providing medical databases. A system is needed that allowscomponents to be ingested, injected, or implanted, as well as worn,carried, or mounted on personal equipment. A system is needed thatprovides alternate input, output, and mounting for a disabled user.

Travelers and outdoor users need a system that provides a variety ofintegrated features. For example, a system is needed that combinestranslation, travel information repository, wildlife recognition,weather, route guidance, local entertainment, and orienteeringfunctions. A system is needed that can provide user identificationfunctions and that can use that identification to provide otherservices, such as transfer of money and product purchasing anddiscounts. Users need a system that can provide personal securityfeatures, such as audible alerts, transmitted alerts, and storingemergency information. A system is also needed that can support militaryneeds.

BRIEF SUMMARY OF THE INVENTION

Our invention satisfies these and other needs by providing a modularpersonal network (MPN). A main aspect of our invention is a system thatallows multiple individual network components (INCs), each with one ormore primary functions, to be used in a wireless personal network, andthat INCs may be added and removed modularly to add or remove functionsof the MPN. This includes the ability to add INCs that were notanticipated when the MPN was first assembled. INCs are personal, in thatthey may be worn, carried, mounted on personal equipment, or otherwiseused in proximity to the person associated with the MPN. Another aspectof our invention is that it supports INCs from different manufacturers,of different models, of different types, and with differentcapabilities. Another aspect is the ability to download software, data,settings, and other information into an INC to control functions of theMPN, and to upload data from an INC. Yet another aspect of our inventionis the use of a common network identifier among the INCs of the MPN, toprevent interference between INCs that may be part of different MPNs,and to prevent the unauthorized use of an INC. Still another aspect ofour invention is a single turn on or turn off command to turn on or offall INCs in an MPN.

Another aspects of our invention is a control unit, which may be an INCcontaining a processor and memory for controlling other INCs in the MPN.Alternatively, there may be no control unit, and each INC may provideits own control. A base station or personal computer may interact withthe MPN, to download software, data, and settings, and to upload datathat may have been collected by the MPN. The MPN may interact with awide area network, such as the Internet, using the base station orpersonal computer in another aspect.

Another aspect of our invention is that one of the INCs may function asa display device. A display INC may be mounted on the back of the wristin a manner similar to a wristwatch, it may be worn on the side of thewrist or hand, or it may be worn in any other suitable location. Theorientation of the display may be changed to suit the needs of the user.In another aspect of our invention, the display INC or other INCs may beworn using a reconfigurable mount that allows easy repositioning andreplacement of the INC.

Another aspect of our invention is that one of the INCs may function asan audio output device, which may provide audio cues, voice, music orother types of audio information. The audio output INC may includeheadphones, ear inserts, or speakers that mount in a hat or headband. Ifmultiple types of audio output are supported, one audio signal may bepaused or muted while the other is generated.

Another aspect of our invention is that one of the INCs may function asa user input device, and may include a device such as a button orpressure sensor, a touch pad and stylus, or a voice input. Pressuresensors may be worn on the hand, fingers, foot, or waist, where they maybe easily operated by tapping.

Another aspect of our invention is that it may be used for one or manypurposes, and that the purposes may be changed as INCs are added orremoved, as software or data is downloaded, or as a user changesactivities. Purposes may include time-related, communications,entertainment, personal organization, guidance, athletic, physicaltherapy, medical, disability-related, travel-related, outdoor-related,identification, security, military, or other purposes or combinations ofpurposes.

Time-related purposes of our invention may include providing the currenttime, multiple time zones, stopwatch functions, and interval timingfunctions, and may also be used to synchronize other functions of theMPN. Communications functions may include communicating with another MPNto provide games, competitions, and to transfer personal information,software, music, and other information. Other communications functionsmay include telephone, paging, instant messaging, and electronic mail.Entertainment functions may include playing recorded music or radio,recording audio or video, or playing a game. Audio, video and imagesrecorded by the user may be linked to other personal data that may havebeen simultaneously collected by the MPN. Personal organizationfunctions may include scheduling appointments, managing contacts,managing a task list, and keeping an electronic journal. An electronicjournal may support text, audio, sketch, image, and video entries, mayautomatically tag journal entries with time or location, may allowjournal entries to be linked to database entries, and may allow journalentries to be uploaded to a personal computer and converted to astandard file format. Guidance functions may include providing position,elevation, and speed information, providing route guidance, andcollecting and annotating position information with text, audio, video,and personal data. Guidance functions may also include recommending anathletic training route based on desired workout parameters, andcomparing personal data collected during multiple sessions.

Athletic functions may include controlling a workout, includingcontrolling individual sections of a workout, and collecting resultsfrom a workout. A coaching interface may provide creation and monitoringof a workout plan. Both music and audio athletic cues may be provided.An INC of the MPN may control a setting on a piece of exerciseequipment, or may collect data from a piece of exercise equipment. TheMPN may measure distance, speed, heart rate, cadence, stride length, andother athletic data. Errors in collected data may be corrected.Secondary performance parameters may be estimated based on collecteddata and other stored information. An athlete may be reminded to consumewater, sodium, food, or other consumables. Two athletes with MPNs may beprovided a competition. The MPN may provide lap counts, workout logging,and other lap swimming functions. The MPN may provide form feedback toan athlete. An athletic journal may also be provided.

Physical therapy functions may include measuring range of motion, doinggait analysis and form feedback, testing muscle strength, monitoringchanges in physical capabilities, and providing a physical therapyjournal. Medical functions may include measuring a metabolic value,detecting a medical problem, controlling a treatment device or takingother medical actions, providing emergency communications, providingstorage of medical databases, and providing a medical journal. INCs maybe worn or carried by a doctor, patient, or nurse, mounted on equipmentsuch as a wheelchair, or implanted, injected, or ingested into apatient. Functions for a disabled user may include alternate outputmethods, alternate input devices, and mounting an INC on a wheelchair orother equipment.

Travel-related functions may include language translation, currencyconversion, time zone conversion, route guidance, local information,guidebook functions, wildlife recognition, a travel journal, weatherinformation, transit information, local entertainment information, andexpense tracking Outdoor-related functions may include direction,position, elevation, route, and weather features. Identity functions mayuse a smart card, personal code, or biometric information to identify auser to another person or system, and may provide exchange of money,product discounts, and purchasing features. Security functions mayinclude an audible alert, an alert message to a public safety facility,and storing emergency contact and emergency medical information.Military functions may include communications, global positioning,guidance, and weather functions.

An MPN is a set of INCs that communicate using a wireless network. TheseINCs use a common communications protocol, such as the Bluetoothprotocol or the IEEE 802.15 standard, to send messages betweenthemselves. Using a common protocol means that the same electroniccomponents and software can be used in each of them, keeping the costlow.

A common protocol also allows new INCs to be added more easily. Thisinvention is “modular,” in that new INCs can be added at any time. Thismay change the function of the overall system. As INCs are added, thesystem's capabilities will grow. As one INC replaces another, thefunctions of the system change accordingly. The system will continue tofunction, with reduced capabilities, as INCs are removed. INCs may bebuilt by various manufacturers, and may have different capabilities.

Our invention is also “personal.” This means that the MPN is small insize, roughly encompassing one person's “personal space.” INCs may beworn by the user, they may be carried by the user, or they may just bein close proximity, for example mounted on personal equipment. Also“personal” is the fact that MPNs provide exactly the functions that theindividual wants, because the combination of INCs is virtuallylimitless.

The MPN may be changed at any time, and the functions of the system maychange correspondingly. For example, a new INC may be added, and a newfunction may be enabled by the system. An INC may be removed, and afunction of the system may be disabled. The system may automaticallydetect a change in the MPN, and correspondingly change the functions.Alternatively, a user may enter a changed configuration, for exampleinto a base station, control unit, or personal computer.

Another advantage of our invention is that it is extensible. This meansthat an INC can be added at any later time, even though that specificINC and its functions may not have been anticipated at the time thesystem was first put together. Each new INC uses the same communicationsmethods and protocols to send and receive data and commands. Thefunctions of the system are controlled by downloaded software. Thismeans that new software can be downloaded to support the unanticipatednew INC.

Software may be downloaded into an INC in the MPN, such as a “controlunit.” The control unit may include memory for holding software anddata, and a processor. The control unit may send commands and data tosome INCs and retrieve data from other INCs. By modifying the softwarein the control unit, the system may support previously unanticipatedINCs. Software may also be downloaded into any other INC.

Software may be downloaded into an INC of the MPN by a personalcomputer. Software on the personal computer may control what isdownloaded. The software on the personal computer may allow extensionsto support unanticipated functions and INCs. The software extensions mayallow the user to specify software modules to download, to configureparameters for the unanticipated INCs, or to perform other functionsrelated to additional INCs and functions.

One of the INCs in the MPN may be a “base station.” This base stationmay used to download information, such as software, data, setup options,and time, into at least one of the other INCs, such as the control unit.The base station may, for example, be connected to a personal computer.The base station, in that embodiment, may provide wireless connectivityto one or more of the other INCs, while the personal computer providesstorage and a user interface for manipulating the information sent toand from the INCs in the MPN. The base station may communicate with thepersonal computer over a standard connection, such as a universal serialbus (USB), serial port, Ethernet, wireless network, infrared, PC Cardinterface, or over a direct connection to the personal computer's bus.

The personal computer may provide a user interface for controlling theINCs in the MPN. For example, the computer may allow the user to specifywhat functions are to be enabled by the system, which may then determinewhat software to download. The user may set configuration parametersthat would then be downloaded to the INC(s) in the MPN.

The base station or personal computer may also have a wide area networkconnection, such as an Internet connection. This may allow anotherperson to control functions of the system. This could include ahealthcare professional, if the system is being used for medicalpurposes. It might include a coach if the system is being used forathletic purposes. It might include a manufacturer or distributor of anyof the INCs in the MPN, who may wish to download software and parametersinto the system to support the INC.

The base station, personal computer, and/or computer over a networkconnection may also be used to upload data from any of the INCs in theMPN, such as a control unit or data collection INC. This data may bestored, modified, analyzed, displayed, or otherwise used on one of thoseother stations.

All of the INCs within a single MPN may be assigned a single uniqueidentifier. This identifier may be downloaded, for example, from a basestation or personal computer to each of the INCs. All communicationsbetween INCs may be tagged with this unique identifier. This willprevent interference between the two MPNs used by two different people.INCs in each system will only listen to messages tagged with that MPN'sown identifier.

The unique identifier can also be used to deter theft and other misuseof any INC. Each INC can be programmed to not accept a different uniqueidentifier without explicit authorization from the authorized user, forexample on a base station or personal computer. The INCs may also beconfigured so that the unique identifier they use cannot be extracted toprogram into a different INC.

All of the INCs in a single MPN may be turned off or on with a singlecommand. For example, a user may press a button or speak a command,which may be received by one of the INCs. The command to turn off may besent to all of the INCs in the MPN. When any INC receives the turn offcommand, it may cease any data collection or control functions, stopsending any wireless communications, go into a low-power mode, andotherwise minimize power use. Other than periodically checking for aturn on message, the INC may cease all communications. The user inputINC may continue monitoring for a turn on indication from the user. Whenthe turn on command is received, the INC may resume its fullcapabilities. This feature may be useful to conserve power, as well asto minimize radio frequency interference in environments, such as on acommercial airliner, where wireless communication may causeinterference.

Our invention may be controlled by a single module configured as acontrol unit. This may be an INC that is worn on the person like theother INCs in the MPN. The control unit may have the facility to allowsoftware to be downloaded into it. The control unit may interface withand control the other INCs in the MPN over the wireless network, basedon the downloaded software. This allows the functions of the system tobe easily modified, simply by downloading different software. Ifdesired, there may be no control unit, and some or all of the INCs maysupport software download. In addition to software or firmware, thecontrol unit (or any other INCs in the MPN) may also allow the downloadof data, setup options and other configuration data, current time, orany other information. The control unit, or other INCs, may also allowthe uploading of data to a base station or personal computer.

The control unit, if present, may be a separate INC, or it may becombined with another of the INCs, such as a display. In some cases, itmay be more efficient to combine the functions of any two of the INCsinto a single INC that provides multiple functions. Alternatively, anyindividual function may be provided by a single INC. The control unit,for example, may be a separate unit, worn on a waistband.

The control unit, if present, preferably has memory and a processor, inaddition to its communication device. This memory and processor supportdownloading of information and software, as well as control of otherINCs in the MPN.

For example, one of the INCs may be a display device. Traditionally,displays worn by a person have been in the form of a wrist display, suchas a wristwatch. However, users of our invention can choose the type ofdisplay that best suits their needs. This may be a display worn on awristband, carried in the hand or pocket, mounted on a piece of exerciseequipment, mounted on a bicycle or in an automobile, or any othersuitable method of carrying by the user. In fact, the user may havemultiple display INCs, and pick the desired one at any time based on aspecific activity.

Traditionally, a wristwatch-type display is worn on the back of thewrist. However, our invention allows the display to be worn or carriedin any manner. For example, a runner who does not wish to turn the wristto view the display may prefer a display that is mounted on the side ofthe wrist or hand, that can be viewed while maintaining proper runningform. The display may be configured so that it can be worn on either theleft or right side. It may be configured so that the top of the displayis oriented toward the thumb, toward the back of the wrist, or at anangle between the two. Alternatively, it may allow the user to configurethe orientation of the display by choosing between one or more options.

Our invention may provide a reusable wearable mount for a display INC orother INCs. This mount may allow the user to easily change one INC foranother, to move the INC, or to reorient the INC.

Wrist displays today, such as wristwatches, typically have inputcontrols and audio outputs built-in. These input controls are often tinyand difficult to use. These audio outputs, since they are located farfrom the user's ear, are often difficult to hear. Our invention does notrequire that these controls and outputs be integrated into the wristdisplay. In fact, our invention encourages each function to be placedwhere it is most usable. For example, the controls may be a set ofswitches, buttons, or other pressure-sensitive devices worn atconvenient points on the body. For example, one sensor can be worn atthe tip of each finger in a glove or partial glove. The user can thenoperate the system by tapping with different fingers or tapping specificsequences to enter different commands to the system. Alternatively, thesensors may be worn at different locations on a waistband, allowing theuser to control the system by tapping different locations on the waist.The sensors may be worn on a foot, so that the system can be operated bytapping a foot. The controls may be mounted on a bicycle or piece ofexercise equipment. Any other suitable types of controls may be used,including dials, levers, keyboards, voice inputs, touch pads and anysuitable combination of multiple types of inputs.

Similarly, an audio output may be provided separately from the displayand other INCs. For example, headphones or earphones may be used.Alternatively, one or more speakers may be worn inside a hat orheadband, providing sound via conduction through the skull. Suchembodiments allow the audio feedback to be loud enough to be easilyheard by the user, even in poor conditions such as being on a busystreet, while keeping the sounds quiet enough to not disturb othernearby people.

The system with an audio output INC may provide an audio outputfunction. For example, music may be stored in a digital form in memoryin the control unit or another INC with a storage capability and sent tothe audio output INC. An INC may also generate audio feedback related toother functions provided by the system. For example, if the system isbeing used for athletic monitoring, audio feedback may be used to promptthe user to work out harder or easier, to provide performanceinformation, or to inform the user what workout zone he or she is in.

The system may provide different audio outputs to signify differentsituations or conditions. For example, different sounds may be generatedfor different situations. Alternatively, different sound sequences maybe generated for different conditions. As yet another embodiment, soundmay be sent to different speakers for different conditions. Voice mayalso be synthesized. Any of these techniques may be combined.

The system may also provide both music and audio feedback. This is anexample of one system providing multiple functions. In this case, themusic may be paused, muted, or the volume may be lowered while the audiofeedback is provided.

Our invention may be used for a wide variety of purposes or combinationof purposes. If desired, one MPN may support different purposes atdifferent times, as INCs are added or removed, as different software anddata are downloaded, as the user performs different activities, etc.

One of the INCs in the MPN may be a clock. The time may be automaticallydownloaded to the clock from a base station or personal computer. Theclock may support functions such as a stopwatch, an interval timer, amultiple event timer, a split timer, etc. The clock may also supportother timing functions in the system, such as measuring speed, cadence,rate of elevation change, heart rate, etc. A clock may also be used tosynchronize functions of the MPN.

The MPN may provide communication functions. For example, multiple MPNsmay be used to send data from one user to another. This may be done, forexample, with the same wireless transmitters and receivers used tocommunicate between INCs in a single MPN, as long as the users are closeenough to each other. Alternatively, a stationary device may coordinatecommunications between two or more users.

Data sent between two systems may enable two or more users to play agame, for example, by sending commands, moves, results, etc. from oneuser to another. Data may allow two or more users to engage in anathletic competition, for example, by transmitting performance databetween athletes. Personal data may also be sent between users, forexample, name, contact information, etc. Users may also exchangerecorded music, software, or any other data.

Our invention may be used to support personal communications. INCs mayinclude a wireless telephone INC or a paging INC. INCs may supportinstant messaging, electronic mail, and other types of textcommunications. INCs may support voice communications or videocommunications. INCs may support transmission and receipt of any type ofdata, including image data, video data, audio data, and text data.

Our invention may be used for entertainment purposes. This may includeallowing a user to play a game, to play music or view other media.

The MPN may allow collection of media data. For example, INCs mayinclude a microphone or a video input. INCs may also include memory oranother storage device to store media. The media collected, such asaudio, video, or still images, may be replayed for the user by one ofthe INCs. The media may be uploaded to a base station or personalcomputer.

The MPN collecting media data may also collect other personal data. Forexample, the system may collect position data, heart rate data, athleticdata such as speed, or other data. The media and personal data may besent using the wireless network to a base station, and into a personalcomputer. The media data may be interpreted by a media interpretationunit or algorithm, such as a speech recognition system. The interpretedmedia data may be used to change the personal data collection functions.

A relationship may be defined when the media and personal data arecollected. For example, the media data may be associated with thepersonal data collected at about the same time as the media wascollected. That relationship may be noted in the data, and maintained asthe data is uploaded to a base station or stored in a personal computer.For example, a voice note or a picture may be tagged as associated withdata collected at a specific time during an athletic workout or othersession.

An MPN may provide personal organizer functions. For example, the systemmay provide appointment scheduling, task management, and contactmanagement. The system may also provide a mobile electronic journal. Ajournal may allow a user to create text or audio entries, and toannotate them with video, still images, audio, or sketches. The entriesmay be automatically tagged with the time and location. The user may beable to link a journal entry to an element in an application specificdatabase, such as a medical database, a health database, a traveldatabase, a music database, a work database, a school database, or adatabase related to any other suitable application. The MPN may supportuploading the journal entries and related data to a personal computer,and converting them to a standard file format for viewing, editing, orprinting on the personal computer. The journal may also include anyother functions or features related to a specific application, such asmedical features, health features, travel features, music features, workfeatures, school features, or any other suitable application features.

Our invention may support guidance features. The MPN may include INCssuch as a global positioning system monitor, an elevation monitor, or acompass. The system may display current location, direction, elevation,speed, or other related information. The system may provide routeguidance, using downloaded map data. The system may collect location,direction, elevation, or speed data. The user may be allowed to annotatethe collected data with audio, video, image, or other types ofinformation. The system may automatically annotate the collected datawith simultaneously collected personal information, such as heart ratedata. The collected data and annotations may be uploaded to a personalcomputer, where they may be displayed. The data may be compared with mapdata. Data from multiple sessions may be compared. The system may usecollected data to recommend a route in a later athletic session, basedon a desired distance, elevation profile, or difficulty, and the usermay be automatically guided through the recommended route. The systemmay also simulate a previous route.

Our invention may provide other athletic functions. For example, aworkout plan may be created on an athlete's computer or a coach'scomputer. The plan may have a specific athletic or health goal, and maybe used to define individual workout sessions. Individual workoutsessions may include multiple sections, each of which may have anindividual goal and individual control characteristics, such a parameterto control, a desired range of values for the parameter, data tocollect, and duration. The control characteristics for a workout sessionmay be downloaded into an INC of the MPN, and the system may use them tocontrol aspects of the workout. Control may be accomplished by promptingthe athlete, by sending a command to a piece of exercise equipment, orother suitable method. The system may use a servo algorithm to controlthe parameter. Results, such as speed, distance, heart rate, data from apiece of exercise equipment or bicycle, and other performance data, maybe collected during the workout. Errors may be detected in the collecteddata, for example based on recognizing invalid sample values.Replacement data may be substituted for the invalid values, for exampleby interpolation. Secondary data, such as cadence, stride length, VO₂max, oxygen uptake, maximum heart rate, percent of maximum heart rate,percent of heart rate reserve, energy consumed, power exerted, orlactate threshold may be derived based on the collected personal dataand other personal data. The collected data or the derived secondarydata may be displayed for the user during a workout, and it may be usedto modify a workout. The data may be uploaded to the athlete's computer,coach's computer, or other suitable location, where it may be stored,displayed, compared between sessions, or otherwise analyzed. Thecollected or uploaded data may be used to modify future workouts.Progress may be measured against the goal of the workout plan. Workoutdata, and other information, may be maintained in a mobile athleticjournal supported by the MPN.

Our invention may provide consumable reminders to an athlete. Forexample, the athlete may be reminded to drink water or a sports drink orto take a sodium supplement, based on metabolic measurements taken ofthe athlete, measurements of the amount of consumable carried, the timesince the most recent reminder, the amount of the consumable carried bythe athlete, or other suitable factors.

One MPN may interface with one or more other MPNs to allow multipleathletes to compete.

The MPN may be configured to provide lap swimming information. By usingone or more monitors worn by the swimmer, the MPN may count laps,distinguish between different strokes, calculate the swimmer's speed,estimate total distance, and provide a log of an entire lap-swimmingworkout.

Our invention may be configured to monitor the form of the athlete, suchas an athlete's running, walking, swimming, bicycling, or rowing form,and provide feedback, either during a training session or afterwards.The form feedback may be based on collecting accelerometer data duringthe training session and comparing it with data representing ideal form.

Our invention may provide physical therapy features. The form feedbackdescribed above may be used to provide gait analysis and other types ofactivity monitoring. The system may also be used to measure range ofmotion, test muscle strength, measure and record changes in physicalcapabilities, provide a therapy journal, or provide other suitablefunctions.

Medical features may also be supported by our invention. The system maymonitor metabolic parameters, such as heart rate, blood oxygen, bloodpressure, temperature, and blood sugar. The monitored parameters andother data may be used to estimate or predict a medical problem. Thesystem may also control a medical device such as a syringe pump ordefibrillator. It may also provide emergency medical communication,provide storage of medical databases, provide a mobile electronicmedical journal, or other suitable medical functions. INCs may be wornor carried by a doctor, patient, or nurse, or mounted on equipment suchas a wheelchair. In addition, an INC may be implanted or injected into apatient, or ingested by a patient. Our invention may also be configuredto support a disabled user. This may include alternate output methods,alternate input devices, and mounting an INC on a wheelchair or otherequipment.

Our invention may provide travel-related functions. These may includelanguage translation, currency conversion, time zone conversion, routeguidance, local information, guidebook functions, weather information,transit information, local entertainment information, and expensetracking Our invention may provide a mobile travel journal. It may alsoprovide automated or semi-automated wildlife recognition. Our inventionmay support users who enjoy outdoor activities. Functions for an outdooruser may include providing orientation (e.g., compass directions),determining position, displaying elevation, and providing routeguidance. The system may provide weather features, such as environmentaltemperature, humidity, and barometric pressure.

Our invention may provide identity functions. The system may identify auser to another person or system. It may use a smart card, personalcode, biometric information, or another suitable method to identify theuser. Based on the identification, the system may provide exchange ofmoney, product discounts, and purchasing features. The identificationmay also be used to prevent unauthorized use of the MPN or any of itsINCs. Other personal security features may be provided. For example, theMPN may provide an audible alert or an alert message to a public safetyfacility. An INC of the MPN may store emergency contact or emergencymedical information, and provide that information when needed. Ourinvention may also support military functions. These may includecommunications, global positioning, route guidance, and weatherfunctions.

Our invention may support multiple purposes within a single MPN. Forexample, one INC may support a function related to athletics, andanother INC may support a function related to personal organization. Asingle INC may be used for multiple purposes. Each user may easilyconfigure his or her own MPN with exactly the INCs that are needed tomeet that user's individual needs. This minimizes cost to each user byallowing him or her to acquire just the INCs that are desired. Also,because similar INCs are used to serve multiple purposes across severaldifferent types of users, the cost of INCs can be held down. Inaddition, because many INCs may use some of the same electroniccomponents, such as power sources and radio frequency transceivers, thecost to manufacture INCs can be minimized.

BRIEF DESCRIPTION OF THE FIGURES

Further features of our invention, its nature and various advantageswill become more apparent upon consideration of the following detaileddescription, taken in conjunction with the accompanying drawings, inwhich like reference characters refer to like parts throughout, and inwhich:

FIGS. 1A and 1B are block diagrams of an illustrative MPN;

FIG. 2A is an illustrative table of manufacturers of INCs of MPNs;

FIG. 2B is an illustrative table of models of INCs;

FIG. 2C is an illustrative table of device types of INCs;

FIG. 2D is an illustrative table of capability types of INCs;

FIGS. 3A through 3J are illustrative message definitions of acommunications protocol that may be used within an MPN;

FIG. 4 is an illustrative data structure that may be used to track INCsin an MPN;

FIG. 5 shows a flow chart of an illustrative process for providing anMPN;

FIGS. 6A and 6B are block diagrams of an illustrative MPN showing howINCs may be added and removed;

FIG. 7 is an illustrative display screen that may be used in configuringan INC of the MPN;

FIG. 8 is a flow chart of an illustrative process showing how anunanticipated INC may be added to an MPN;

FIG. 9 is a flow chart of an illustrative process showing how data maybe downloaded to an INC of an MPN;

FIG. 10 is an illustration showing how two illustrative MPNs mayinteract;

FIG. 11 is a block diagram of an illustrative MPN showing how an INC maybe programmed with a common network identifier;

FIGS. 12 and 13 are illustrative display screens that may be used in theprogramming of a common network identifier into an INC of an MPN;

FIG. 14 is a flow chart of an illustrative process for using a commonnetwork identifier within an MPN;

FIG. 15 is a block diagram showing how an MPN may communicate with abase station and a personal computer;

FIG. 16 is a flow chart of an illustrative process for uploadinginformation from an INC of an MPN;

FIG. 17 is a block diagram of a portion of an MPN showing the use of acontrol unit;

FIG. 18 is a flow chart of an illustrative process for using a controlunit as an INC of an MPN;

FIG. 19 is a flow chart of an illustrative process for providingpersonal components in an MPN;

FIGS. 20A through 20C show illustrative mounting means for INCs in anMPN;

FIG. 21 is a flow chart of an illustrative process for using an INCmounted on a piece of exercise equipment in an MPN;

FIGS. 22A through 22C show illustrative means for mounting a displaydevice which is an INC in an MPN;

FIGS. 23A through 23F show additional illustrative means for mounting adisplay device which is an INC in an MPN;

FIGS. 24A and 24B are flow charts of an illustrative process forproviding a display device as an INC of an MPN;

FIG. 25 is a flow chart of an illustrative process for providing areusable wearable mount for use with various INCs of an MPN;

FIGS. 26A through 26C show illustrative mounts that may be used withvarious INCs of an MPN;

FIGS. 27A through 27D show illustrative display devices that may be usedas INCs in an MPN;

FIGS. 28A through 28D show illustrative audio output devices that may beused as INCs in an MPN;

FIG. 29 is a flow chart of an illustrative process for providing anaudio output device as an INC in an MPN;

FIG. 30 is a flow chart of an illustrative process for providing a userinput device as an INC in an MPN;

FIGS. 31A through 31C show illustrative means for mounting a user inputdevice which is an INC in an MPN;

FIG. 32 is a flow chart of an illustrative process for using an MPN formultiple purposes;

FIG. 33 is a flow chart of an illustrative process for using an MPN fortime-related purposes;

FIG. 34 is a block diagram of an illustrative MPN with a clock function;

FIG. 35 is an illustrative display screen that may be shown with the MPNof FIG. 34;

FIG. 36 is a flow chart of an illustrative process for using an MPN witha communication function;

FIG. 37 is a flow chart of an illustrative process for communicatingbetween MPNs;

FIGS. 38 and 39 are illustrations of communications between multipleMPNs;

FIG. 40 is a flow chart of an illustrative process for using an MPN withan entertainment function;

FIG. 41 is a flow chart of an illustrative process for using an MPN withpersonal organization features;

FIG. 42 is a flow chart of an illustrative process for using an MPN toprovide a mobile electronic journal;

FIGS. 43A and 43B are flow charts of illustrative processes for using anMPN to provide a guidance function;

FIG. 44 is a diagram of an illustrative MPN that may be used to providea guidance function;

FIGS. 45A through 45L show illustrative screens that may be provided byan MPN in providing a guidance function;

FIGS. 46 through 49 show illustrative screens that may be used with amodular personal computer that provides a guidance function;

FIG. 50 is a flow chart of an illustrative process for providing anathletic function in an MPN;

FIG. 51 is a flow chart of an illustrative process for providing workoutcontrol and feedback using an MPN;

FIG. 52 is a block diagram of an illustrative system for communicatingbetween a personal computer and an INC of an MPN;

FIG. 53 is a block diagram of an illustrative MPN that controls aspectsof an athletic workout and collecting results from a workout;

FIG. 54 is a block diagram of an illustrative system for communicatingamong an MPN, an athlete's personal computer, and a coach's personalcomputer;

FIG. 55 is a diagram of an illustrative MPN that may be used to providecontrol of an athletic workout and collect workout results;

FIG. 56 is a flow chart of an illustrative process for managing aworkout plan used with an MPN;

FIG. 57 is a flow chart of an illustrative process for defining workoutparameters used in an MPN;

FIG. 58 is an illustrative screen that may be shown for defining aworkout to be used with an MPN;

FIG. 59 is an illustrative data structure that may be used to storeinformation about a workout session to be controlled using an MPN;

FIG. 60 is a flow chart of an illustrative process for controllingmultiple sections of a workout using an MPN;

FIG. 61 is a flow chart of an illustrative process for estimating aderived performance parameter using stored information;

FIG. 62 is a diagram of an illustrative MPN that may be used to measurea primary performance parameter and estimate a secondary performanceparameter;

FIG. 63 is an illustrative display screen that may be displayed to allowthe entry of personal data to be used with an MPN;

FIGS. 64A through 64F show illustrative display screens that may bedisplayed by a display INC in an MPN during an athletic effort;

FIG. 65 is a diagram of an illustrative MPN that may be used to collectdata and that may detect invalid data and estimate replacement data forthe invalid data;

FIG. 66 is a flow chart of an illustrative process for estimatingreplacement data for invalid collected data;

FIG. 67 is an example of heart beat data that may have been collected byan MPN;

FIGS. 68A and 68B show an example of collected heart rate data withinvalid samples and an example of replacement data;

FIGS. 69A and 69B show illustrative display screen that may showcollected primary and secondary data with replacement data for invalidsamples;

FIG. 70 is a flow chart of an illustrative process for providing anathlete with cadence and stride information using an MPN;

FIG. 71 is a flow chart of an illustrative process for providingconsumption reminders to an athlete;

FIG. 72 is a diagram of an illustrative MPN that may be used to provideconsumable reminders to an athlete;

FIG. 73 is an illustrative display screen that may be used by an MPN toprovide a consumable reminder;

FIG. 74 is a flow chart of an illustrative process for providingswimming-related information using an MPN;

FIG. 75 is a diagram of an illustrative MPN that may be used to providelap swimming information;

FIGS. 76A and 76B are illustrative display screens that may be used byan MPN to provide lap swimming information;

FIG. 77 is an illustrative display screen that may be shown inconjunction with an MPN used for collecting swimming-relatedinformation;

FIG. 78 is a flow chart of an illustrative process for providing gait orform feedback using an MPN;

FIG. 79 is a diagram of an illustrative MPN that may be used to provideform feedback during a training activity;

FIGS. 80A through 80C are illustrative display screens that may be shownto a user by an MPN to provide form feedback during a training activity;

FIG. 81 is an illustrative display screen that may be shown inconjunction with an MPN used for providing gait or form feedback;

FIG. 82 is a flow chart of an illustrative process for providing anathletic training journal using an MPN;

FIG. 83 is a flow chart of an illustrative process for providingphysical therapy functions using an MPN;

FIG. 84 is a flow chart of an illustrative process for providing medicalfunctions using an MPN;

FIG. 85 is a flow chart of an illustrative process for estimating amedical problem using an MPN;

FIG. 86 is a flow chart of an illustrative process for providing amobile electronic medical journal using an MPN;

FIG. 87 is an illustrative block diagram of a mobile electronic medicaljournal;

FIG. 88 is a flow chart of an illustrative process for providingfeatures for a disabled user with an MPN;

FIG. 89 is a flow chart of an illustrative process for providingtravel-related functions using an MPN;

FIG. 90 is an illustrative block diagram of an MPN that may be used toprovide travel-related functions;

FIG. 91 is a flow chart of an illustrative process for providing amobile electronic travel journal using an MPN;

FIG. 92 is a flow chart of an illustrative process for assisting a userin identifying wildlife using an MPN;

FIG. 93 is a flow chart of an illustrative process for providingoutdoor-related functions using an MPN;

FIG. 94 is a flow chart of an illustrative process for providingidentification functions using an MPN;

FIG. 95 is a flow chart of an illustrative process for providingsecurity functions using an MPN;

FIG. 96 is a flow chart of an illustrative process for providingmilitary functions using an MPN;

FIG. 97 is an illustrative diagram of an MPN that may be used to providemultiple functions;

FIG. 98 is a flow chart of an illustrative process for providing music,media collection, and personal data collection using an MPN;

FIG. 99 is an illustrative data structure that may be used to storepersonal data and related media data;

FIG. 100 is an illustrative overview of the MPN; and

FIGS. 101A and 101B are flow charts of an illustrative process forturning off and turning on an MPN.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 100 shows an overview of how an illustrative modular personalnetwork (MPN) may be used. The MPN is associated with a user 1. The MPNmay include multiple individual network components (INCs), each of whichmay have one or more primary functions. Each INC may include a wirelesstransceiver for communicating with other INCs in the MPN. The wirelessnetwork may be associated with user 1, for example, within a few metersof the user. Each INC may be worn or carried by user 1, or otherwise inthe user's immediate vicinity. For example, INC 2, which may be worn onthe user's waist, may be a control unit that includes a processor andmemory, to store and run software to control other INCs in the MPN. INC3, which may be worn on the user's hand or wrist, may be a displaydevice. If desired, a variety of mountings may be provided to allow thedisplay to be seen optimally in variety of circumstances, such asmounting on the side of the hand or wrist. If desired, a reusable mountmay allow a display or other INC to be easily repositioned, reoriented,and replaced. INC 4, which may be a headset or may be worn in a headbandor hat, may be an audio output device. One or more speakers may be wornin the ear, or may be worn against the skin near the ear. The audiooutput device may support output of tones, music, or voice. Audio cuesof various types may be generated. If desired, the audio output devicemay provide multiple types of audio output. One output may be paused ormuted while the other is provided. INCs 5, 7, and 7 may be user inputdevices. Any suitable type of user input may be provided, such as voiceinput, buttons, a portable keyboard, or a stylus. As shown, pressuresensors are worn in the fingertips of a glove, and are operated bytapping with the fingers. Different commands may be indicated by tappingwith different fingers or in different sequences. If desired, suchpressure sensors may be worn on the hand, at the waist, on the foot, orin any other suitable manner. INC 8 may provide another function for theuser, such as an input function, an output function, a storage function,or a control function. As many or as few INCs may be included in the MPNas desired. If desired, one or more INCs may be removed from the MPN toremove functions, and one or more INCs, such as INC 9, may be added toadd other functions. The changed configuration may be determineddynamically or the changes may be indicated by the user.

Second user 10 may have a second MPN. For example, second user 10 may beriding a bicycle. INC 11 may be mounted on the handlebars of the bicycleand may include display functions, user input functions, and controlunit functions. INC 12 may be an audio output device, mounted on seconduser 10's helmet. INC 13 may be a sensor mounted on the bicycle tomeasure its speed. When second user 10 comes into range of first user1's MPN, there is no interference. Each INC in either MPN is programmedwith a network identifier that is common to all INCs in the MPN butunique among different MPNs. Each message sent from one INC in an MPN toanother INC in the same MPN may be tagged with the common networkidentifier or with a unique component identifier of the target INC, sothat no unintended INCs process the message. In addition, the networkidentifier may be stored in secure memory in each INC, so that the INCcannot be used in a different MPN without explicit authorization fromthe user who programmed the network identifier.

The MPN may interface with a more stationary device, such as basestation 15 or personal computer 16. Base station 15 may act as part ofthe MPN when the MPN is within range. Base station 15 may include awireless communication device to communicate with one or more of theINCs in the MPN. Alternatively, base station 15 may communicate with oneof the INCs using another means, such as a serial cable, USB, a dockingstation, infrared, or other connection. Personal computer 16 maycommunicate with base station 15. Alternatively, personal computer 16may communicate directly with one or more INCs, acting as a basestation. Personal computer 16 or base station 15 may download software,data, settings, and other information to one or more INCs. For example,software may be downloaded to control one or more INCs, or to implementone or more features. As unanticipated INCs are added to the MPN, newsoftware modules may be downloaded to control and interface with them,and an application on personal computer 16 may be used to configuresettings related to the new INCs. Personal computer 16 and base station15 may be used to program the common network identifier into each INC inthe MPN. Data may be uploaded from one or more INCs to personal computer16 to be stored, displayed, or analyzed. If desired, personal computer16 may communicate with another computer 18 over a wide area network 17,such as the Internet. Software, data, settings, and other informationmay be sent from computer 18 to personal computer 16 for use with theMPN, and data from the MPN may be sent from personal computer 16 tocomputer 18.

An MPN may be used for one or more purposes. For example, the MPN maysupport a global turn on or turn off feature, in which all activedevices may be disabled or re-enabled with a single command to a singleINC. The MPN may provide clock functions 20, such as providing thecurrent time and date, supporting multiple time zones, providingstopwatch features, and synchronizing other features of the MPN. The MPNmay provide communication functions 25, such as communicating withanother MPN to support games, competitions, and other types of datatransfers, telephone features, paging features, instant messaging, andelectronic mail. The MPN may provide entertainment functions 30, such asplaying music, recording audio and video media, and games. The MPN mayprovide personal organization functions 35, such as schedulingappointments, managing contacts, tracking tasks, and maintaining amobile electronic journal. The MPN may support guidance functions 40,such as showing current position, speed, and elevation, providing routeguidance, collecting and annotating position and speed data, andrecommending an athletic training route. The MPN may support athleticfunctions 45, such as supporting a workout plan, supporting workoutdefinition, controlling a workout, communicating with exerciseequipment, collecting athletic data, detecting and correcting errors incollected data, estimating secondary data based on collected data,providing competition between users of multiple MPNs, logging lap swimworkouts, providing form feedback, and providing an athletic trainingjournal.

The MPN may support physical therapy and medical functions 50, such asmeasuring range of motion, gait analysis, measuring muscle strength,measuring changes in physical therapy, monitoring a metabolic value,detecting a medical problem, controlling a treatment device, providingemergency communication, storing medical databases, providing anelectronic medical journal, and supporting INCs that may be injected,ingested, or implanted. The MPN may provide disabled access 55, such asalternate input devices, alternate output devices, and alternate INCmounting means. The MPN may support travel functions 60, such aslanguage translation, currency conversion, time zone conversion, routeguidance, local information, guidebook features, wildlife recognition, amobile electronic travel journal, weather information, local transit andentertainment schedules, and expense tracking The MPN may supportoutdoor functions 65, such as compass direction, geographical location,route guidance, elevation reporting, and weather features. The MPN maysupport identity functions 70, such as identifying a user to anotheruser or another system, providing exchange of money, providing productdiscounts, and providing product purchasing. The MPN may supportpersonal security functions 75, such as an audible alert, an alertmessage to a public safety facility, and storage of emergencyinformation. The MPN may support military functions 80, such ascommunications, geographical position, route guidance, and weatherfeatures. The MPN may support combinations of functions, and itsfunctions may vary over time as INCs are added or removed, as differentsoftware or data is downloaded, or as the user's needs change.

FIG. 1A shows a block diagram of illustrative MPN 100A. This MPNincludes INCs 110A, 110B, 110C, and 110/d. Each INC includescommunication device 120, for communicating with other INCs overwireless communication path 140. Communication device 120 may be, forexample, a standard radio frequency wireless transceiver with a rangeappropriate for a personal network (e.g., between six feet and sixtyfeet). Communication device 120 may also include hardware and softwareimplementing a standard wireless protocol, such as Bluetooth or IEEE802.15. An antenna may be included. If desired, transmitter and receivermay be separate devices. Not shown in each INC is a power source.

Each INC also includes one or more other functions 130-137. These otherfunctions may be provided by hardware and/or software incorporated intothe INC. The software may be firmware provided with the INC, or it maybe downloaded into the INC over communication path 140 or using othermeans.

FIG. 1B shows how MPN 100A may be modified to become MPN 100B. In themodified MPN, INC 110C has been removed, and INC 110E has been added.Correspondingly, other function 135 associated with INC 110C is nolonger available, and other functions 138 and 139 associated with INC110E are now available.

Different manufacturers may manufacture INCs. Each manufacturer may beassigned a unique manufacturer identifier, as shown in table 210 of FIG.2A. Each manufacturer may provide various types of INCs, each of whichmay be assigned a model identifier by the manufacturer, as shown intable 220 of FIG. 2B. The model identifier may be unique for a specificmanufacturer.

There may also be defined a set of device types, as shown in table 230of FIG. 2C. The device type identifiers may be standard across allmanufacturers and models. For example, Model 3 by Manufacturer 2 mayhave the same device type as Model 7 by Manufacturer 12. Device typesmay be divided into a range for input devices 234 and a range for outputdevices 232. It may also have ranges 236 and 238 for manufacturers touse when a standard device type has not yet been assigned. An INC mayhave multiple device types, if it has multiple functions 130-139 (FIG.1).

For each device type, there may be a standard set of definedcapabilities, which may or may not be supported by any specific INC withthat device type. For example, as shown in table 240 of FIG. 2D, devicetype 257, which may be an audio output INC, may have three standardcapabilities, any of which may or may not be supported by any particularaudio output INC. Capability 242 may be the ability to output stereoaudio. Capability 244 may be the ability to control the output volume ofthe audio. Capability 246 may specify the number of volume incrementssupported by a particular INC. These capabilities are merelyillustrative.

The manufacturer identifier, model identifier, one or more device types,and any supported device capabilities and values may be stored inread-only memory in the INC, and provided over communication path 140(FIG. 1), to allow the INC to be identified by another INC.

FIGS. 3A through 3J illustrate an exemplary communications protocol thatmay be used between INCs in an MPN. The protocol may include a definedset of messages that may be sent from one INC to another. This messageprotocol may be encapsulated in one or more lower-level protocols, suchas Bluetooth or IEEE 801.15. If desired, this protocol may function ondifferent lower-level protocols in different environments.

As shown in FIG. 3A, each message may include message type 301 and errordetection/correction fields 302. Message type 301 may indicate to thereceiving INC how to process the message. Error detection/correction mayinclude parity, checksums, cyclic redundance checks (CRCs), or othermechanisms for detecting that a received message has one or more errors,and possibly correcting the error(s).

Identity request message 300 of FIG. 3A may be sent by an INC (such as acontrol unit or base station) wishing to determine the identity andcharacteristics of one or more other INCs in the MPN. For example, thismessage may be broadcast and all other INCs in the MPN may respond.Identity request message 300 may include a unique network identifier 303common to all INCs in the MPN. It may include a network address 304 ofthe INC sending the request. Each INC in the MPN may have a networkaddress that is unique among all INCs in the MPN. Identity requestmessage 300 may also include controller identifier 305. This may be anidentifier that is unique across all INCs, and it may correspond to thecontrol unit, base station, or other INC that is sending the message.

Component identity message 310 of FIG. 3B may be sent by an INC inresponse to identity request message 300. It may include networkidentifier 311 of the INC sending the message. Network identifier 311may be the same as the network identifier 303 in the requesting message,if both INCs are part of the same MPN. It may be blank if this INC hasnot yet been assigned to an MPN. It may be different if this INC belongsto a different MPN. If this INC has been assigned to an MPN, componentidentity message 310 may also include network address 312.

Component identity message 310 may also include information about thetype of INC and its capabilities that may be stored in read-only memoryin the INC. For example, the message may include component identifier313, which may be the identifier for this INC that is unique across allINCs. The message may also include manufacturer identifier 314, modelidentifier 315, one or more device types 316, and capability list 317.

Net address assignment message 320 of FIG. 3C may be sent by a controlunit, base station, or other INC to configure a newly detected INC tofunction within the MPN. It may include controller identifier 305. Itmay include the new network identifier 321 and network address 322 to beprogrammed into the INC. It may include component identifier 313 toensure that the correct INC processes the message. It may also includesecurity code 323 to ensure that unauthorized personnel do not changethe network identifier and network address.

On processing net address assignment message 320, the INC may respondwith network acknowledgement message 330 of FIG. 3D. This message mayrepeat component identifier 313, network identifier 321, and networkaddress 322, to inform the controller that the operation was successful.Alternatively, the message may include a field indicating success orfailure of the operation, and the reason for failure if it was notsuccessful.

Output data request message 340 of FIG. 3E may be sent to an INC that iscapable of outputting. It may include the network identifier 321 andnetwork address 322 of the INC that is to perform the output function.The message may include request serial number 341. This number may beused by the requesting INC and the outputting INC to keep track ofmultiple pending requests. Output data request message 340 may includedevice type 316 and capability type 317 to inform an INC that supportsmultiple output functions how to process the data. Output data requestmessage 340 may also include the data to output 342. The format of thisdata may depend on the type of INC receiving the data and how it is tobe processed.

After processing output data request message 340, the output INC mayrespond with output acknowledgement message 350 of FIG. 3F. This messagemay include network identifier 321, network address 322, and requestserial number 341 to allow the controller to determine which requestthis acknowledgement corresponds to. It may also include acknowledgementcode 351, which may indicate whether the request was processedcorrectly, and if not successful may include a reason for the failure.

Input data request message 360 of FIG. 3G may be sent to an INC that iscapable of inputting. It may include the network identifier 321 andnetwork address 322 of the INC that is to perform the input function.The message may include request serial number 361. This number may beused by the requesting INC and the inputting INC to keep track ofmultiple pending requests. Input data request message 360 may includedevice type 316 and capability type 317 to inform an INC that supportsmultiple input functions how to process the data.

After processing input data request message 360, the input INC mayrespond with input acknowledgement message 370 of FIG. 3H. This messagemay include network identifier 321, network address 322, and requestserial number 361 to allow the controller to determine which requestthis acknowledgement corresponds to. It may include acknowledgement code371, which may indicate whether the request was processed correctly, andif not successful may include a reason for the failure. It may alsoinclude the requested data 372, formatted as appropriate for the deviceand data type.

An INC may also send unsolicited data message 380 of FIG. 3I. Thismessage may be sent when the INC has acquired some data for which theremay be an ongoing request, or when the INC has entered a state, such asan error condition, that needs to be reported to a control unit, basestation, or other INC. This message may include the network identifier321 and network address 322 of the INC. It may include device type 316and capability type 317 to allow the receiving INC to know how toprocess the data. It may also include data 381, formatted as appropriatefor the device type and capability type.

A control unit, base station, or other INC may periodically send outnetwork poll message 390 of FIG. 3J. This message is sent to determinewhether an INC is still present on the MPN. It may include networkidentifier 321 and network address 322 of the INC being polled. Thepolled INC may respond with component identity message 310 or othersuitable message.

The message types shown in FIGS. 3A through 3J are merely illustrative.Other types of messages may be defined and sent between INCs in the MPN.For example, a command may be sent to turn on an INC or to turn off anINC. If desired, a command may be broadcast to all INCs in an MPN,rather than addressed to a specific INC.

Table 400 of FIG. 4 shows an illustrative data structure that may bemaintained by a control unit, base station, or other INC to track INCson the MPN. If desired, multiple INCs in the MPN may maintain suchinformation. Column 410 may hold the network address of each INC. Column420 may hold the component identifier of each INC. Column 430 may holdthe manufacturer identifier of the INC. Column 440 may hold the modelidentifier of the INC. Column 450 may hold the device type of each INC.Multiple device types may be stored for a single INC if desired. Column460 may hold a list of capability types for each device type listed foreach INC. Column 460 may also hold specific values related to eachcapability type. Column 470 may hold a flag indicating whether the INCis currently active. For example, if an INC has not recently respondedto a network poll message 390 (FIG. 3J), flag 470 may be changed toindicate that the INC is no longer active. If an INC responds to anidentity request message 300 (FIG. 3A), the INC may be added to table400 if it is not already present, and flag 470 may be set indicatingthat the INC is active.

Table 400 is merely illustrative. Other columns may be included. Otherdata structures may be used. If desired, this information may be storedin multiple data structures.

FIG. 5 shows flow chart 500 of an illustrative process for providing anMPN. All steps are optional and may be performed in any suitable order.In step 510, multiple INCs may be provided. This may include substep 514of providing wireless communications with each INC. It may also includesubstep 512 of providing at least one primary function for each INC. Theprimary function may correspond to other function 130-139 (FIGS. 1A and1B). If desired, an INC may include multiple primary functions.Alternatively, an INC may include a primary function, a secondaryfunction, etc.

In step 520, INCs may be changed dynamically. This may include substep522 in which an INC may be removed. It may also include substep 524 inwhich a new INC may be added. In step 530, the change may be detectedautomatically, for example using messages 300 through 390 of thecommunications protocol of FIGS. 3A through 3J. The system mayalternatively allow a user to enter information about the change in step535. For example, a user may add or remove an entry for an INC from aconfiguration screen on a personal computer.

In step 540, the functions of the MPN may be adjusted to compensate forthe change. In substep 542, this may include removing a function fromthe MPN that may have been provided (or partly provided) by the removedINC. In substep 544, this may also include adding a function to the MPNthat may be at least partly supported by the new INC.

FIG. 6A shows illustrative MPN 600 showing how software may bedownloaded to control INCs. MPN 600 may interface with personal computer610 to control downloading and configuration functions.

Personal computer 610 may include control application 620, which may beconfigured to control downloading to an MPN and configuring variousaspects of MPN functions. Control application 620 may support plug-insfor different types of INCs. For example, plug-in A 622 may supportdownloading code to support INC A 650. Plug-in A 622 may support loadingdriver A 626, for example from local storage such as a compact disk orover the Internet, as well as downloading driver A 626. It may alsosupport configuring INC A 650, as well as downloading data to anduploading data from INC A 650.

Personal computer 610 may include communications device 612 forcommunicating with one of the INCs, such as a control unit 630, usingcommunication path 670. Control unit 630 may include communicationsdevice 632 for communicating with personal computer 610. Communicationsdevice 612, communications device 632, and communication path 670 maybe, for example: a docking station and connector; a Universal Serial Bus(USB) port; infrared transmitters and receivers; serial ports; Ethernetconnectors; radio frequency (RF) transceivers; or any other suitablecommunications means. If desired, communications may be performedwirelessly, and communications device 632 may be the same as wirelesscommunications device 636 used to communicate between control unit 630and other INCs.

One of the INCs may be a control unit 630. Control unit 630 may includeprocessor 634 and memory 638, as well as communications device 632 forcommunicating with personal computer 610, and wireless communicationsdevice 636 for communicating with other INCs over wireless communicationpath 675. Memory 638 may hold control software 640 which may includefirmware, operating system, boot software, communication software, andthe like. Memory 638 may also hold downloaded driver A 626 forcontrolling INC A 650.

MPN 600 may also include INC A 650. This component may include wirelesscommunications device 652 for communicating with control unit 630 andother INCs over wireless communication path 675. INC A 650 may alsoinclude device hardware and firmware 654 for performing one or moreprimary functions of the INC.

In operation, a user may run control application 620 on personalcomputer 610. The user may load and run plug-in A 622 to configure MPN600 to function with INC 650. The user may load driver A 626 anddownload it to control unit 630. Control unit 630 may subsequently usedownloaded driver A 626 to control the functions of INC A 650. The usermay also use plug-in A 622 to configure aspects of INC A 650, todownload data to the INC, to upload data that may have been collected bythe INC, or to perform other functions related to INC A 650.

In FIG. 6B, INC B 660 has been added to MPN, creating new MPNconfiguration 605. INC B 660 may include wireless communications device662 for communicating with control unit 630 and other INCs over wirelesscommunication path 675. It may also include device hardware and firmware664 for performing one or more primary functions associated with INC B660.

Plug-in B 624 may be loaded into control application 620 on personalcomputer 610, for controlling aspects of INC B 660. Driver B 628 may beloaded into personal computer 610 and downloaded into control unit 630for subsequently controlling INC B 660.

Although FIGS. 6A and 6B show drivers being downloaded into a controlunit, software may alternatively be downloaded into any of the INCs, forexample, if control unit 630 is not present.

FIG. 7 shows illustrative screen 700 of MPN 600 (FIG. 6A) that may bedisplayed by control application 620 and plug-in A 622 on personalcomputer 610. Menu bar 710 may allow the user to access variousapplication functions, such as file functions, security functions,device functions, system functions, help functions, and the like. Item720 may display information about the INC, such as the name of themanufacturer, the model number, capabilities, and other suitableinformation. Item 730 may display the version number of the deviceplug-in currently loaded on personal computer 610. Button 735 may allowthe user to download the selected driver to control unit 630 or otherINC. Button 737 may allow the user to load a more recent driver from theInternet. Region 740 may allow the user to set various configurationparameters associated with the INC. For example, region 742 may allowthe user to enter text for a first parameter. Selection 745 may allowthe user to select from a set of options for a second parameter. Thisscreen is purely illustrative and may be configured and designed in anysuitable manner.

FIG. 8 shows flow chart 800 of an illustrative process to allow anunanticipated INC to be added to the MPN. For example, after a user hasseveral INCs of an MPN, a new INC with a new capability may bemanufactured. The user does not need to discard any existing INCs; theycan continue to be used just as they have been. The unanticipated INCcan be added to the MPN and the capabilities of the MPN will be expandedto encompass the capabilities of the new INC.

All steps are optional and may be performed in any suitable order. Instep 810, the unanticipated INC may be added to the MPN. The system maydetect the INC using an identity request message 300 (FIG. 3A). In step820, a software application may be run, for example on a personalcomputer, which controls downloading software objects to INCs. In step830, that application may be used to download the specific softwareobject to control the unanticipated INC. In step 840, software may bedownloaded to control the unanticipated INC. The software may bedownloaded, for example, to a control unit. Alternatively, the softwaremay be downloaded to the unanticipated INC itself. In substep 842,multiple software objects may be downloaded, one of which may controlthe unanticipated INC. Other software objects may be used to controlother INCs, or to perform other MPN functions. In step 850, a softwareextension, such as a plug-in, may be provided to the softwareapplication. In step 860, the user may be allowed to configure the newINC and the downloaded software object, using the software applicationand the software extension.

Flow chart 900 of FIG. 9 shows an illustrative process for downloadingdata to control an INC. All steps are optional and may be performed inany suitable order. In step 910, software may be downloaded. In step912, data may be downloaded. In step 914, setup options may bedownloaded. In step 916, the current time may be downloaded. If desired,other suitable types of data may be downloaded as well.

In step 920, data may be downloaded over a network, such as theInternet. For example, software or other data may be downloaded from anInternet site into a personal computer. In step 922, data may bedownloaded from a computer, such as a personal computer. In step 924,data may be downloaded from a base station. A base station may be astationary device that communicates with one or more INCs. The basestation may be independent, or it may be connected to a personalcomputer. In step 930, the data may be downloaded into the INC to becontrolled. In step 932, the data may be downloaded into a control unit.The control unit may be an INC configured with a processor and memory tocontrol aspects of other INCs in the MPN. The control unit may sendinformation or commands to the INC in step 934. In step 940, thedownloaded data may be used to modify one or more functions of the INC.

Software and other data may also be downloaded, for example into acontrol unit, to coordinate the functions of multiple INCs.

FIG. 10 shows how two MPNs 1000 and 1050 may interact. First MPN 1000may include audio output INC 1010, display INC 1012, control unit 1014,and accelerometer 1016. Second MPN 1050 may include display 1060, heartrate sensor 1062, and control unit 1064. Any of the INCs of either MPNmay send a message intended for one or more INCs of the same MPN. TheINCs of the other MPN may need to ignore the message. For example,control unit 1014 may send data to display 1012 to be displayed. Display1060 will ignore the message, because it did not originate within secondMPN 1050. Similarly, heart rate monitor 1062 may send heart rate data tocontrol unit 1064 for processing. Control unit 1014 will ignore thedata, as it did not originate within first MPN 1000. The configurationof these two MPNs is merely illustrative, and all INCs are optional.

FIG. 11 shows illustrative partial MPN 1100, illustrating how an INC1130 may be programmed with a common network identifier using a basestation 1110. Base station 1110 may be a personal computer, a cardinstalled in a personal computer, a docking station connected to apersonal computer over a connection such as USB, a standalone device, orany other suitable configuration. Base station 1110 may include memory1120, which may be random access memory, a hard disk, or other suitablememory. Base station 1110 may also include communications device 1112,which may be a wireless communications device similar to thecommunications device in each of the other INCs, or may be any otherwired or wireless connection.

Memory 1120 may be used to hold a common network identifier to be usedwithin all INCs of a single MPN. It may also be used to hold informationabout the various INCs that have been configured using base station1110.

INC 1130 may be a new INC, which has not yet been assigned a networkidentifier. Alternatively, it may already have been assigned a networkidentifier, which may be stored in secure memory 1140. Secure memory1140 may be memory that can only be read or written by INC 1130, andcannot be accessed without a security code.

A user of base station 1110 may indicate that INC 1130 is to beprogrammed with the base station's network identifier. The user may makethis indication by, for example, bringing INC 1130 into proximity ofbase station 1110, making a physical connection between base station1110 and INC 1130, pressing a button on base station 1110, making a menuselection on base station 1110 (for example, if base station 1110 is apersonal computer or is connected to a personal computer), or by takingother suitable actions. The user may also be required to enter apersonal code, or to invoke other security measures to ensure his or herproper identity. Base station 1110 may then send a message to INC 1130with the new common network identifier and the proper security code. IfINC 1130 is a new INC, it may store the security code and the networkidentifier in secure memory 1140. If it has previously been programmedwith a network identifier, it may compare its stored security code withthe security code it just received, and if they match may store the newnetwork identifier.

If desired, INC 1130 may also incorporate an algorithm to prevent alarge number of consecutive attempts at changing the network identifier.For example, if INC 1130 receives more than three unsuccessful attemptsto change the network identifier within a ten-minute period, it may lockout any further attempts for the next thirty minutes.

Using this configuration a user may assign any new INC into his or herMPN. A user may also move an INC from one MPN to another, but only withthe authorization of the original owner of the INC.

FIG. 12 shows illustrative screen 1200 that may be shown by base station1110 (FIG. 11) or personal computer to allow an INC 1130 to bepersonalized with the user's network identifier. The user may be allowedto enter a security code in screen region 1210. When the security codehas been verified, and the security code and network identifier havebeen successfully sent to the INC 1130, the system may display overlay1220.

FIG. 13 shows illustrative screen 1300 that may be shown by base station1110 (FIG. 11) or personal computer to allow INC 1130 to be programmedwith a different network identifier when it already has a networkidentifier stored in secure memory 1140. The user may be prompted for asecurity code in screen region 1310, as well as the old security codeused to program INC 1130 with the previous network identifier in region1320. When the security codes have been verified, and the security codeand network identifier have been successfully sent to the INC 1130, thesystem may display overlay 1330.

These screens are purely illustrative and may be configured and designedin any suitable manner.

FIG. 14 shows flow chart 1400 of an illustrative process to use a commonnetwork identifier among INCs in an MPN. All steps are optional and maybe performed in any suitable order. In step 1410, each INC may beprogrammed with a common network identifier. This may be done with abase station, personal computer, or other device. The programming mayuse appropriate security to ensure that an unauthorized user cannotreprogram the network identifier in any INC.

In step 1420, any messages sent from a first INC in the MPN to a secondINC in the same MPN may contain the network identifier stored within thefirst INC. The second INC, on receiving the message, may compare thenetwork identifier within the message to the network identifier storedin the secure memory in the second INC. If the two identifiers aredifferent, the message may be ignored. If the two identifiers are thesame, the second INC may assume that the message originated from an INCwithin the same MPN, and may process the message if appropriate.

In step 1430, an INC may be moved from one MPN to another. This mayinvolve changing the network identifier stored in the INC to a newvalue. To do this may require explicit authorization from a user, insubstep 1432. It may also require the entry of a password or code oranother security measure to ensure that the user is authorized to makethe change, in substep 1434.

FIG. 15 shows extended MPN 1500. This block diagram shows how an MPN mayinterface with other systems. MPN 1500 may include control unit 1510.The use of control unit 1510 is merely illustrative. Any other suitableINC may be used. Control unit 1510 may include wireless communicationsdevice 1512 for communicating over wireless communications paths 1546and 1547 with other INCs within the MPN. Control unit 1510 may alsoinclude one or more other functions 1514, which may include a processorand memory for controlling other INCs in the MPN. MPN 1500 may alsoinclude INCs 1520 and 1530. These INCs may include wirelesscommunications devices 1522 and 1532, respectively. Each may include oneor more other functions 1524 and 1534, respectively.

Control unit 1510, and other INCs, may communicate over communicationpath 1545 with base station 1540. As shown, communications path 1545 maybe a wireless communications path. Alternatively, base station 1540 maycommunication with one or more INCs using any suitable wired path. Basestation 1540 may include communications device 1542 for communicatingwith control unit 1510 and other INCs, and a second communicationsdevice 1544 for communicating over communication path 1555 with personalcomputer 1550. If desired, communications device 1542 and communicationsdevice 1544 may be the same device. Communications device 1544 maycommunicate with communications device 1556 on personal computer 1550using any suitable physical and logical protocol. This may include aserial port, USB, infrared, radio frequency, a docking station, or othermeans.

In addition to communications device 1556, personal computer 1550 mayhave display 1552, keyboard 1553, mouse, printer 1554, and modem 1551.Modem 1551 may be any suitable type of connection to a wide areanetwork, and may include a telephone modem, a digital subscriber linemodem, a cable modem, an Ethernet hub, and Ethernet router, or othersuitable equipment. Personal computer 1550 may connect using path 1565to wide area communications network 1560, which may be the Internet.Personal computer 1550 may be configured to send or receive informationfrom another computer using wide area network 1560.

FIG. 16 shows flow chart 1600 of an illustrative process for uploadinginformation from an INC. All steps are optional and may be performed inany suitable order. In step 1610, information may be reported by an INC.That information may have been collected by the INC, for example using asensor within the INC. Alternatively, the information may have beengenerated by the INC. In step 1615, the information may be received by acontrol unit, which may be another INC within the same MPN. Theinformation may be sent from the control unit, or any other suitableINC, to a base station in step 1620, and to a personal computer in step1622. If desired, any of the control unit, base station, and personalcomputer may be omitted, or their functions may be combined in anysuitable manner. If desired, the collected information may be sent overa communications network, such as the Internet, in step 1624, andreceived by another computer.

In step 1630, the information may be stored, for example by the basestation, the personal computer, or by another computer accessed over thecommunications network. The information may be displayed for a user. Theinformation may be analyzed, in step 1632. In step 1640, the uploadedinformation may be used, at least in part, to create information todownload. This derived information may be downloaded to the same INCthat originated the uploaded data, to the control unit, or to anotherINC in the MPN. Refer to the description of FIG. 9 above for stepsrelated to downloading of data.

FIG. 17 shows a more detailed block diagram 1700 of a portion of MPN1500 of FIG. 15. Base station 1540, control unit 1510, and INC 1520 areshown. It can be seen that control unit 1510 includes processor 1742 andmemory 1744. INC 1720, which is an audio output INC, is also shown.Audio output INC 1720 includes wireless communications device 1722 forcommunicating over wireless communication path 1730 with control unit1510 and other INCs. Audio output INC 1720 also includesdigital-to-analog converter 1724, for converting digital audio data toan analog audio signal, and speaker 1726 for playing the analog audiosignal audibly. The INCs shown are merely illustrative.

FIG. 18 shows flow chart 1800 of illustrative process for using an INCthat is a control unit in an MPN. All steps are optional and may beperformed in any suitable order. In step 1810, the control unit may beconfigured to be worn. It may be attached, for example, to a waistband,a wristband, an armband, or other worn in another suitable location. Ifdesired, the control unit may alternatively be carried, mounted onpersonal equipment, or otherwise associated with the user. Informationmay be downloaded to the control unit, for example from a base stationor personal computer. In step 1820, software may be downloaded to thecontrol unit. In step 1822, data may be downloaded to the control unit.In step 1824, configuration parameters may be downloaded to the controlunit. In step 1826, the date and/or time may be downloaded to thecontrol unit.

In step 1830, data may be sent from the control unit to another INCwithin the MPN. For example, any of the data sent to the control unit insteps 1820, 1822, 1824, or 1826 may be sent to another INC. The controlunit may also send information to another INC that is derived fromdownloaded data, from data collected from other INCs, or other suitabledata.

In step 1832, the control unit may control a function of another INC.The control unit may accomplish this by sending one or more messages tothe other INC, and possibly by receiving messages in response. Thecontrol may be based on downloaded software, downloaded data, downloadedparameters, time, or any derived data.

In step 1834, the control unit may collect data from another INC. Thecontrol unit may request the data by sending a message to the other INC.Alternatively, the other INC may send the data unsolicited. The data maybe a single item, or it may consist of several samples collected over aperiod of time. The control unit may process the data, combine datasamples, combine data from multiple INCs, or otherwise modify thecollected data. In step 1850, data may be uploaded from the controlunit, for example to a base station or personal computer. This mayincluded collected data, derived data, or data generated by the controlunit.

In step 1860, functions of the control unit may be integrated with otherfunctions. For example, the control unit may also have a display or auser input device. The control unit may also include clock functions, instep 1840, and it may track time to coordinate functions of the MPN, toschedule actions, and to tag collected data. The control unit may treatthe other integrated functions as though they were in another INC,without the need to send and receive wireless messages to communicatewith them.

In step 1870, the control unit may support multiple other INCs withmultiple functions. Some may be input INCs, some may be output INCs, andsome may be a combination. Some INCs may be wholly contained withoutexternal input or output, such as a storage INC or a data processingINC. The control unit may maintain a table of active INCs, andcommunicate with the other INCs as required. The control unit mayautomatically detect when an INC is added to the MPN or removed from theMPN. When an INC is added to the MPN, the control unit may ignore ituntil it receives downloaded software or data related to the new INC.Alternatively, it may automatically make use of the capabilities of thenew INC. When a INC is removed from the MPN, the control unit may waitfor a period of time to make sure that communications with the INC werenot temporarily lost. The control unit may continue functioning withreduced functions. In addition or alternatively it may generate an alertto the user.

If desired, an MPN need not include a control unit. Some or all of thefunctions of a control unit may be incorporated into one or more of theother INCs. If desired, each INC may provide its own control. Ifdesired, software, data, configuration settings, and other informationmay be downloaded directly into some or all of the INCs by a basestation or personal computer prior to mobile use.

FIG. 19 shows flow chart 1900 of an illustrative process for providingpersonal INCs in an MPN. All steps are optional and may be performed inany suitable order. In step 1910, the user may wear an INC. For example,in substep 1912, the user may wear an INC on a hand, wrist, arm, leg,foot, waist, head, or other suitable part of the body. The INC may beworn on an article of clothing in substep 1914, such as a glove, apartial glove, a wristband, an armband, a hat, a headband, a shirt, awaistband, a shoe, or other suitable item of clothing.

In step 1920, the INC may be mounted on personal equipment that may beused by the user. For example, in substep 1922, the INC may be mountedon a bicycle, a car, a piece of exercise equipment, or other suitablepersonal equipment. The INC may provide an input or output functionassociated with the personal equipment.

In step 1930, the MPN may also include a relatively stationary INC, suchas a base station or personal computer. The base station or personalcomputer may function as part of the MPN while the user is in proximityto the device. The communications connection with the stationary devicemay be the same wireless network used to communicate between the INCs,or it may be another type of connection. The other type of communicationmay be a docking station or other fixed method, USB or other wiredmethod, or infrared or other wireless method. The stationary device mayonly support communications with one of the mobile INCs, such as acontrol unit, or it may support communications with several orsubstantially all of the INCs.

FIGS. 20A through 20C show several illustrative methods for mountingINCs. For example, FIG. 20A shows some options for allowing a user 2005to wear INCs. INC 2012, which may be an audio output INC, may be mountedon headband 2010. INC 2022, which may be a display, may be mounted onwristband 2020. INC 2032, which may be a user control, may be mounted onglove 2030. INC 2042, which may be a control unit, may be mounted onwaistband 2040. INC 2052, which may be an accelerometer, may be mountedon shoe 2050. These INCs and options for wearing are merelyillustrative. Other options may be used if desired. The user 2005 maydecide what functions will be provided simply by choosing to wear aspecific set of INCs at any given time.

FIG. 20B shows some options for mounting INCs on a piece of exerciseequipment 2070. For example, INC 2074 may be an input sensor to readdata associated with the exercise equipment, or may be an output INC tocontrol aspects of the exercise equipment. INC 2072 may be a displayINC, or may be configured to communicate with a processor embeddedwithin the exercise equipment. These INCs may function as part of theMPN when the user is on or near the device.

FIG. 20C shows options for mounting INCs on a bicycle 2060. For example,INC 2062 may be a display INC. INC 2064 may be a sensor for measuringpedaling cadence. INC 2066 may be a sensor for measuring wheel speed.These INCs may function as part of the MPN when the user is on or nearthe bicycle.

The options shown in FIGS. 20A through 20C are merely illustrative.Other types of INCs, other types of mounting, and other types ofpersonal equipment may be supported if desired.

FIG. 21 shows flow chart 2100 of an illustrative process for using anINC mounted on a piece of exercise equipment. All steps are optional andmay be performed in any suitable order. In step 2110, the INC may bemounted on a piece of exercise equipment. In substep 2112, the INC maybe mounted on a bicycle. The INC may function as part of the user's MPNwhen the user is near or on the exercise equipment. In step 2120,control commands may be sent to the INC mounted on the exerciseequipment. The INC may control the function of the exercise equipmentdirectly, or it may send a command to the exercise equipment, forexample using a serial port or radio frequency transmitter. As shown insubstep 2122, the command may be to control the difficulty of theexercise, such as by changing a resistance setting, a speed setting, aslope setting, or the like. The control command may also be to a displayINC or other user output INC mounted on the exercise equipment. In step2130, data may be collected from the INC. The INC may measure thecollected data directly, or it may retrieve the data from the exerciseequipment, for example using a serial port or radio frequency receiver.The data may be, for example, pedal speed of a bicycle in substep 2132or wheel speed of a bicycle in substep 2134. In substep 2136, otherperformance information may be collected from the exercise equipment,such as speed, power, or heart rate. The data may be collected, forexample, using a sensor attached to the exercise equipment or bicycle,or by communicating with a processor embedded in the exercise equipment.The collected data may be stored, it may be displayed, and it may beused to modify a workout. If desired, the collected data may be uploadedto a base station or personal computer, where it may be stored,displayed, or analyzed.

An INC may function as a display INC. A display INC may be worn orcarried by the user or mounted on a piece of personal equipment. Adisplay INC may be combined with other functions, such as user controls,audio output, or a control unit, or the INC may function solely as adisplay INC. A single display INC may be used to display different typesof information at different times, depending on the other INCs in theMPN. The display INC may not need to be changed to provide new types ofinformation display. Rather this may be accomplished by adding a new INCwith a new function, downloading new software into the display INC or acontrol unit, or otherwise modifying other parts of the MPN. Inaddition, the user may switch to a different style of display INCwithout changing any other part of the MPN, and maintain all preexistingMPN settings and functions.

The display INC may include a wireless communications device forcommunicating with other INCs in the MPN. For example, the display INCmay receive display commands and data from one of the other INCs, suchas a control unit. The display INC may incorporate any appropriatedisplay technology, such as liquid crystal displays (LCDs), lightemitting diodes (LEDs), etc. It may also include means for mounting theINC to the user's body. If desired, a display INC may accept differenttypes of input for display, such as text, bit-map or other graphics,video data, instructions to turn on or off specific visual indicators,instructions to turn on or off various display modes, or other suitabledisplay items and instructions.

In a mounting similar to a wristwatch, a display INC 2215 may be mountedon the back of a wrist 2210, using wristband 2220, as shown in FIG. 22A.FIG. 22B shows a variation, in which display INC 2235 is mounted on theside of wrist 2230, using wristband 2240. In another variation shown inFIG. 22C, display INC 2255 may be mounted on the back of hand 2250 usingpartial glove 2260. In these examples, the display INCs are shown todisplay time. However, any suitable information appropriate to thefunctions provided by the INCs of the MPN may be shown on the displayINC.

FIGS. 23A through 23F show how a display INC may be worn on the side ofa hand, and may be configured with various orientations. For example, inFIGS. 23A through 23C, the display INC may be configured to be orientedtoward the back of the hand, toward the fingertips, or at an anglebetween them, respectively. In these FIGS., the display is shown on theleft hand. Alternatively, the display may be configured to be worn onthe right hand, as shown in FIGS. 23D through 23F. Different users withdifferent needs may desire displays worn on opposite hands, in differentpositions on the hand or wrist, and at different orientations. Some, forexample, may wish to wear the display in the traditional wristwatchposition and orientation on the back of the wrist. Others, for exampleathletes, may desire a display that can be quickly viewed on the side ofthe hand without having to twist the arm. The preferred orientation maydepend on the user's activity.

A display may be provided in which the user may configure the positionand/or orientation. For example, a user may wish to switch the displaybetween the left wrist/hand and the right wrist/hand. A user may also beallowed to change the orientation of the display. For example, if thedisplay is implemented using a dot-matrix liquid crystal display (LCD),the software within the MPN may support multiple orientations. A displaymay also be provided with multiple mounts—e.g., wristbands, partialgloves, and the like.

FIG. 24A shows flow chart 2400 of an illustrative process for providinga display as an INC in an MPN. All steps are optional and may beperformed in any suitable order. In step 2410, a display may be providedas an INC. The INC may include a wireless communications device forcommunicating with other INCs in the MPN. If desired, the display may becombined with one or more other functions into a single INC, sharing asingle wireless communications device. In step 2415, the display INC maybe configured to be worn, for example on a wristband, partial glove, orthe like. In step 2420, the display INC may be configured to be mountedon an item of personal equipment. That may include, for example, a carin substep 2424, a bicycle in substep 2422, or a piece of exerciseequipment in substep 2426. In step 2430, the user may be allowed tochange the mounting of the display INC. For example, multiple mounts maybe provided so that the display INC may be moved from one part of thebody to another, or from the wrist to a piece of exercise equipment.

FIG. 24B shows a flow chart with illustrative expanded detailed of step2415, in which the display INC may be worn by the user. All steps areoptional and may be performed in any suitable order. In step 2460, thedisplay may be configured to be worn on a hand or wrist. For example, awristband or partial glove may be provided. If desired, the display maybe worn on other parts of the body instead of the hand or wrist. In step2465, the display may be configured to be worn on the side of the handor wrist, allowing the display to be viewed more easily, for example byan athlete. In step 2470, the display and mount may be configured toallow the display to be worn on either the left or right hand or wrist.

In step 2480, the display may be oriented in a direction desirable tothe user. For example, in substep 2482, the display may be orientedtoward the fingertips. In substep 2484, the display may be orientedtoward the back of the hand or wrist. In substep 2486, the display maybe oriented at an angle between those two options. In step 2490, theorientation of the display may be configurable by a user, allowing theuser to select from one or more orientation options.

FIG. 25 shows illustrative flow chart 2500 of an illustrative processfor providing a reusable wearable mount that may be used with variousINCs, such as a display INC. This method may allow the user to usedifferent mounts or displays to match clothing, to use displays withdifferent functions, and to quickly and easily change the position andorientation of the display.

All steps are optional and may be performed in any suitable order. Instep 2510, a reusable mount may be provided that may be worn on theuser's body. In step 2515, the mount may be provided as part of anarticle of clothing, such as a glove, partial glove, wristband,waistband, shirt, or any other suitable article of clothing. In step2520, the mount may use a hook and loop type of fastener. If desired,any other suitable type of fastener may be used on the article ofclothing. In step 2525, the mount may be made directly to the user'sskin. For example, a non-toxic adhesive may be used on the back of theINC to be mounted.

In step 2530, a plurality of mounts may be provided. For example, insubstep 2532, mounts may be manufactured in different styles or colors.In substep 2534, mounts may be manufactured to be worn on differentparts of the body. A user may choose one of the mounts based on style,whim, convenience, function, or for any other reason.

In step 2540, the mount may be used with an INC. The user maytemporarily attach the INC to the mount. If desired, the mount may alsobe configured to allow devices that are not INCs to be attached. In step2545, the INC attached to the mount may be a display INC. The displayINC may be used to display current time and other information that maybe provided by the MPN. In step 2550, the user may be allowed toreposition the INC on the mount. For example, the user may be allowed tochange the placement and orientation of a display INC to make it moreconvenient to read the displayed information. In step 2560, the user maybe allowed to mount various INCs onto a single mount. The INCs may bemanufactured with different shapes, materials, colors, styles,functions, or otherwise may be of different value to a user at differenttimes.

FIGS. 26A through 26C show various examples of reconfigurable wearablemounts that may be provided. FIG. 26A shows a wristband with a buckle.FIG. 26B shows a partial glove. FIG. 26C shows a stretchable band thatmay be looped around the hand and over the thumb. Each of these mountsmay be manufactured with an area of hook and loop fasteners, where themount includes, for example, the hook portion, and the loop portion ison the back of the INC to be mounted.

FIGS. 27A through 27D show various display INCs that may be used withthe mounts of FIGS. 26A through 26C. These displays may have differentshapes, different materials, different functions (for example showingeither time or heart rate), or may otherwise differ. Each of the INCsmay provide the means to fasten to the mount, for example the loopportion of a hook and loop fastener.

An INC may function as an audio output INC. An audio output INC may beworn or carried by the user or mounted on a piece of personal equipment.The audio output INC may be combined with other functions, such as usercontrols, display, or a control unit, or the INC may function solely asan audio output INC. A single audio output INC may be used to outputdifferent types of information at different times, depending on theother INCs in the MPN. The audio output INC may not need to be changedto provide new types of information output. Rather this may beaccomplished by adding a new INC with a new function, downloading newsoftware into the audio output INC or a control unit, or otherwisemodifying other parts of the MPN. In addition, the user may switch to adifferent style of audio output INC without changing any other part ofthe MPN, and maintain all preexisting MPN functions.

The audio output INC may include a wireless communications device forcommunicating with other INCs in the MPN. For example, the audio outputINC may receive digital audio data from one of the other INCs, such as acontrol unit. The audio output INC may include a digital-to-analogconverter (DAC) for converting the digital audio data to an analog audiosignal. Alternatively, the audio output INC may receive an analog audiosignal from another INC. It may include one or more amplifiers and oneor more speakers. It may also include means for mounting the INC to theuser's body. If desired, the audio output INC may also include moreadvanced audio processing capabilities, including speech synthesis,recognition of various audio file formats, decryption of secure dataformats, the ability to generate any of a predefined set of tones oraudio segments, or other suitable circuits and algorithms.

FIGS. 28A through 28D show various types of audio output INC that may beused with an MPN. FIG. 28A shows an audio output INC configured as apair of headphones 2810. It may include two speakers 2812 and 2814. Awireless communications device, DAC, and amplifiers may also beincluded. The headphones may also be configured as two separate INCs,which may each communicate wirelessly with control unit and other INCs.Each INC may have its own DAC, amplifier, and speaker. Headphones may beprovided with connecting bar, or they may be configured as small modulesto be inserted inside the ear and worn independently.

FIG. 28B shows audio output INC 2822 that may be configured to be wornwith a headband 2820. The audio output INC may be worn near the ear sothat minimal power is needed to drive its speaker. Sound from thespeaker may be provided via conduction through the skull. FIG. 28C showstwo independent audio output INCs 2832 and 2834, which may be worn witha headband 2830, to provide stereo sound. In FIG. 28D, audio output INC2844 may be configured to be worn with hat 2840. If desired, hat 2840may be configured to function with two audio output INCs (not shown).The audio output INC of FIGS. 28B through 28D may be configured to fitinto the ear, or to lie flat across the skin near the ear. The headbandor hat may be designed to hold the audio output INC or INCs in place inthe ear, or to hold the audio output INC in place against the skin wheresound may be conducted through the skull. If desired, the headband orhat and the audio output INC may be jointly designed so that the audiooutput INC may be repositioned to best meet the user's needs, and sothat alternate designs of audio output INCs may be used with the samemount.

FIG. 29 shows flow chart 2900 of an illustrative process for providingan audio output INC in an MPN. All steps are optional and may beperformed in any suitable order. In step 2910 an audio output INC may beprovided. Audio output INC may include a wireless communications devicefor receiving audio data and other audio commands from one or more otherINCs in the MPN. It may include DAC, one or more amplifiers, and one ormore speakers. It may also include speech synthesis circuitry, tonegeneration circuitry, digital audio file processing capability,decryption circuitry, a library of audio segments, or other suitablesubsystems.

In step 2920, the audio output INC may be configured to be worn. Forexample, in substep 2922, it may be configured as a headset. In substep2924, it may be configured as one or more independent earphones, forexample to be inserted inside an ear. In substep 2926, it may beconfigured to be worn with a hat. In substep 2928, it may be configuredto be worn with a headband. In step 2930, the audio output INC mayinclude one or more speakers. For example, it may be configured toprovide stereo sound. Alternatively, multiple audio output INCs may beincluded as separate INCs in a single MPN, and may be controlledindependently.

In step 2932, audio output INC may provide music. Music may be providedin stereo. In step 2934, synthesized voice may be provided. Thesynthesized voice may be provided to the audio output INC as digital oranalog audio. Alternatively, the voice may be provided to the INC inanother form, such as text or phonemes, and the audio output INC maycreate the synthesized voice. In step 2936, tones may be output. Thetones may be provided to the audio output INC as digital or analogaudio. Alternatively, the tones may be provided to the INC in anotherform, such as waveform descriptions or indexes into a table ofpredefined audio segments, and the audio output INC may create thetones.

In step 2940, the audio output INC may be used by the MPN to provideaudio cues to the user. The audio cues may be for any purposeappropriate to the functions provided by the MPN and its other INCs. Forexample, cues may be provided to an athlete with performance information2941, workout zone information 2942, workout prompt 2943, or changeintensity prompt 2944. Route prompt 2945 or direction alert 2947 may beprovided by an MPN that provides route guidance. Medical alert 2946 maybe provided by an MPN that monitors medical conditions. Communicationalert (e.g., notification of an incoming telephone call or message) 2948and voice communication 2949 may be provided by an MPN that providescommunication services.

In step 2950, sound may be used to indicate different conditions ordifferent audio cues. For example, in substep 2952, different sounds(e.g., different tones) may be used to indicate different conditions. Insubstep 2954, different sound sequences may be used to indicatedifferent conditions. In substep 2956, sound may be sent to differentspeakers or audio output INCs to indicate different conditions.

In step 2960, the audio output INC may be used for multiple purposessimultaneously. For example, in a system that provides both music andaudible athletic workout feedback, both may be sent to the same audiooutput INC or INCs. When an audio cue, such as workout feedback, isoutput, the music may be muted in substep 2962 or the volume of themusic may be lowered in substep 2964. Alternatively, the music may bepaused in substep 2966 while the audio cue is presented. The volumechanging or pausing of the music may be controlled, for example, by acontrol unit. For example, the control unit may send both music andaudio cues to the audio output INC, and may send commands to the audiooutput INC to control the volume of both. To pause the music, which maybe stored in digital form in memory in the control unit, the controlunit may temporarily stop reading music data from its memory while theaudio cue is presented, and then resume reading the music data fromwhere it was left off. If desired, the pausing, muting, or volumereduction of the music itself may constitute the audio cue, with noadditional sound generated. For example, the system may pause the musiconce for two seconds as one type of cue, and pause the music three timesfor one half second each time as a second type of cue.

In step 2970, an audio output INC may be provided separately from adisplay INC. This may be an advantage over many existing systems inwhich these two functions are combined into a single unit worn on thewrist. In these prior art devices, either the sound volume is so loudthat it disturbs other nearby people, or it is too soft to be heard bythe user at all times. In this invention, the audio output INC can beprovided close to the ear, and the volume can be kept low while stillallowing the user to hear the audio even in poor environmentalconditions. If desired, the MPN may include the ability for a user tocontrol the volume of audio output. The system may also allow a user toindependently control the volume of different types of audio output. Forexample, the volume of the music may be controlled separately from thevolume of the audio cues, and both of those may be controlled separatelyfrom the volume of voice communications.

In substep 2975, cues may be sent to either the audio output INC asaudio cues, or to the display INC as visual cues, or both. The user maybe allowed to configure where different types of cues are sent.

An INC may function as a user input INC. A user input INC may be worn orcarried by the user or mounted on a piece of personal equipment. Theuser input INC may be combined with other functions, such as a displayor control unit, or the INC may function solely as a user input INC. Asingle user input INC may be used to input different types ofinformation at different times, depending on the other INCs in the MPN.The user input INC may not need to be changed to provide new types ofinformation input. Rather this may be accomplished by adding a new INCwith a new function, downloading new software into the user input INC ora control unit, or otherwise modifying other parts of the MPN. Inaddition, the user may switch to a different style of user input INCwithout changing any other part of the MPN, and maintain all preexistingMPN functions. An MPN may include multiple user input INCs, which may beof similar types or of different types.

The user input INC may include a wireless communications device forcommunicating with other INCs in the MPN. For example, the user inputINC may send digital commands or data to one of the other INCs, such asa control unit. The user input INC may include an analog-to-digitalconverter (ADC) for converting analog inputs to digital data. It mayalso include means for mounting the INC to the user's body. If desired,the user input INC may also include more advanced input processingcapabilities, including voice recognition, tensile, audible, or visualfeedback of input commands, anticipation of likely commands, groupingand combining of similar inputs, or other suitable circuits andalgorithms.

FIG. 30 shows flow chart 3000 of an illustrative process for providing auser input INC in an MPN. All steps are optional and may be performed inany suitable order. In step 3010, a user input INC may be provided. Instep 3020, the user input INC may be separate from other INCs, such as adisplay INC or a control unit. This may be an advantage to some users.For example, in many prior art systems the user controls are mounted ona display device worn on the wrist. Controls may be small and closetogether, and may require the user to look at the display device tooperate it. This requires to user to twist the arm, to look and find thecontrols, and to reach one hand over to the other. These actions may notbe convenient for all users at all times. For example, an athlete mayneed to operate a system using the minimum possible motions, and withouthaving to change the direction he or she is looking. If desired, usercontrols may be combined with any other INC.

In step 3020, any suitable type of user input INC may be used.Preferably, the INC is one that may be used in a mobile environment. Forexample, a computer keyboard and mouse may not be appropriate except asattached to a personal computer or base station that may be used attimes with the MPN. Appropriate types of input INC may include apressure sensor or button 3021, multiple pressure sensors or buttons3022, a touch pad 3023, a stylus 3024 used for example with a touch pad,a portable keyboard 3025, and a microphone 3026. Microphone 3026 may beused to capture audio data, or it may include speech recognitioncircuitry. If desired, an MPN may include multiple user input INCs. Forexample, one system may include several buttons, a microphone withspeech recognition, and a touch pad with a stylus.

In step 3030, the user input INC may be configured to be worn orcarried. For example, a pressure sensor may be attached to a fingertip3032, hand 3031, foot 3035, or waist 3034. A touch pad or microphone maybe worn at the waist 3034. A microphone may be worn on the wrist 3033 orother part of the arm, or may be configured as part of a headset. Ifdesired, the user input INC may be designed to be mounted on an item ofclothing in step 3040, such as glove 3041, partial glove 3042, wristband3043, waistband 3044, or footband 3045, shoe, or sock. The user inputINC may also be mounted on an item of personal equipment in step 3050,such as on a car 3051, bicycle 3052, or exercise equipment 3053.

In step 3060, if user input INC includes one or more pressure sensors orbuttons, it may be operated by tapping. For example, the user may mounta pressure sensor on one or more fingertips, and they may be operated bytapping the fingertip against the palm of the hand, the thumb, otherpart of the body, or another surface. The user may mount a pressuresensor on the palm of the hand and operate it by tapping it with afingertip, with the other hand, hitting another part of the body, orstriking another surface. The user may mount a pressure sensor on awaistband and operate it by tapping it. The user may mount a pressuresensor on the foot and operate it by tapping an object with the toe orby pushing off the wall while swimming laps in a swimming pool. Insubstep 3062, the user may tap different sensors for different commands.For example, an athlete may tap with the sensor on one finger to startand stop a stopwatch function, and tap with the sensor on a differentfinger to capture a single lap split time. In substep 3064, the user maytap different sequences to indicate different commands. For example, theuser may tap once, twice in quick succession, or other suitablesequences. In substep 3066, the user may tap a specific combination ofsensors simultaneously to input a specific command.

FIGS. 31A through 31C show several illustrative methods for mounting auser input INC. In FIG. 31A, pressure sensors 3110, 3111, 3112, 3113,3114, and 3120 are mounted on a user's hand 3100. If desired, they mayalso be mounted on a glove or partial glove worn by the user. In thisconfiguration, any single sensor may be operated independently. Inaddition, combinations of sensors may be operated simultaneously. Forexample, a user may tap the thumb with the forefinger and simultaneouslyoperate both sensor 3110 and sensor 3111. The user may alsosimultaneously strike a surface with one, two, or more sensors toprovide various input commands.

FIG. 31B shows pressure sensor 3134 mounted to a user's foot 3130 usingfootband 3132. This configuration may be useful to a swimmer, who maytap the wall of a swimming pool to count laps, and may tap the bottom ofthe pool to indicate other commands.

FIG. 31C shows user 3140 who has mounted two input INCs 3144 and 3146 onwaistband 3142. These input INCs may be pressure sensors and may beoperated by tapping. Alternatively, these INCs may include a microphone,portable keyboard, touchpad and stylus, or other input INC carried onthe waist and retrieved for use. Any suitable combination of input INCsand mounts may be used.

An MPN may be used for many purposes. A single MPN may be used for asingle purpose, or it may be used for multiple purposes. The uses of theMPN may change over time, as the user adds and removes INCs, downloadsor removes software, changes configuration parameters, or just changeshow he or she interacts with the system. A single INC may have a singlepurpose, or it may be used for multiple purposes. Some types of INCs,such as control units INCs, display INCs, audio output INCs, and userinput INCs, may be general purpose.

FIG. 32 shows a flow chart of an illustrative process for using an MPNfor multiple purposes. All steps are optional and may be performed inany suitable order. In step 3205, the MPN may be used to provide atime-related function. In step 3208, the MPN may be used to provide aguidance function. In step 3210, the MPN may be used to provide anathletic function. In step 3215, the MPN may be used to provide amedical function. In step 3220, the MPN may be used to provide anentertainment function. In step 3225, the MPN may be used to provide anoutdoor-related function. In step 3230, the MPN may be used to provide acommunications function. In step 3235, the MPN may be used to provide apersonal organization function. In step 3240, the MPN may be used toprovide an identification function. In step 3245, the MPN may be used toprovide a personal security function. In step 3250, the MPN may be usedto provide a military function. In step 3255, the MPN may be used toprovide a physical therapy function. In step 3260, the MPN may be usedto provide a disability-related function. In step 3265, the MPN may beused to provide a travel-related function. In step 3270, the MPN may beused to provide multiple functions. This may include substep 3272 ofproviding multiple functions with a single MPN configuration. It mayalso include substep 3274 of providing multiple functions with multipleMPN configurations. The functions shown in FIG. 32 are merelyillustrative. Other functions may be provided if desired.

Step 3205, providing time-related functions, is shown in more detail inFIG. 33. All steps are optional and may be performed in any suitableorder. In step 3310, a clock may be provided as part of an MPN. This mayinclude substep 3312 in which the clock is provided as part of anotherINC, such as a control unit or display INC. In step 3320, the currentdate and time may be downloaded into the INC. This may include substep3322 in which the current time is downloaded over the wireless network,for example from a personal computer. Alternatively, it may includesubstep 3324 in which the INC include a radio receiver to acquire thecurrent time from station WWV time of day radio broadcast.

In step 3330, the INC may provide a clock function. This may includedisplaying the current day and time on a display INC. The INC mayinclude a time zone function in step 3331. This may include displayingthe current time in multiple time zones, or converting a time from onetime zone to another. In step 3332, the INC may provide a stopwatchfunction. This may include allowing the user to time individual events.It may include step 3334 of providing a split timer function, in whichthe user is allowed to time individual portions of an event. It may alsoinclude step 3335 in which the user is allowed to time multiple events.In step 3333, the system may provide an interval timer function,allowing the user to mark one or more recurring intervals of specificdurations.

In step 3340, the system may store collected time information. This mayinclude collected stopwatch, split, and event times. This collected datamay be tagged with the date and time on which it was stored. The usermay also be allowed to input descriptive data related to the collectedtime data. The stored data may also include time zone settings,intervals settings, or other settings. In step 3342, the collected timeinformation may be uploaded, for example to a base station or personalcomputer.

In step 3350, the clock functions may be used to synchronize other MPNfunctions. For example, a control unit may collect data from aparticular INC on a regular interval, or update a display once persecond. The control unit may be allowed to read the current time fromthe clock. The clock may also be configured to provide an unsolicitedinterrupt to the control unit or other INC at a regular interval. Instep 3352, data collected from other INCs may be tagged with the currenttime retrieved from the clock.

FIG. 34 shows a block diagram of an illustrative MPN 3400 with a clockfunction. In this system, the clock 3420 is embedded in the control unit3410. Clock information is sent to a separate display INC 3430, whichmay output the information on display 3440. User commands, such aschanging clock mode and starting and stopping the stopwatch, areprovided by buttons 3460 on a separate input INC 3450. The input INC3450 may be worn on the hand, the control unit/clock 3410 may be worn onthe waist, and the display INC 3440 may be worn on the wrist.

FIG. 35 shows an illustrative screen 3500 that may be shown on display3440 (FIG. 34). Mode list 3520 may list the available clock modes. Inthis case, the system may support a time mode, a zone mode (e.g., timezone), a stopwatch mode, an interval timer mode, and an event timermode. Indicator 3530 may show the currently active mode, in this casethe time mode. The user may change to a different mode by pressing oneof buttons 3460 (FIG. 34). The current time 3510 may be displayed whilein time mode.

More details of step 3230 (FIG. 32), providing a communication functionin an MPN, are shown in FIG. 36. All steps are optional and may beperformed in any suitable order. In step 3610, communication may beprovided with another MPN. This may be accomplished if one of the INCsin the MPN includes a communications device capable of communicatingwith an INC of another MPN. The wireless communications device used forcommunicating among the INCs within an MPN may also be used forcommunicating with another MPN, if the user of that MPN is in closeproximity. The system may be configured to accept messages with thespecific network identifier associated with the other MPN, while thecommunications are in progress.

In step 3620, wireless telephone communications may be provided, if oneof the INCs includes a wireless telephone. The audio output INC for theMPN may output the incoming audio from a telephone call, and amicrophone used as a user input INC for the MPN may be used to providethe outgoing audio for the telephone call. This allows the telephone INCitself to be smaller and less costly, since it does not require abuilt-in speaker or microphone.

In step 3625, paging services may be provided. For example, one of theINCs may include a paging receiver. Text pages may be shown on thedisplay INC. Audio alerts and voice pages may be sent to the audiooutput INC. Two-way paging may be provided if desired. An instantmessaging function may be provided in step 3630, with one INC receivingtext messages for display on the display INC, and another INC allowingtext messages to be composed and sent to another person elsewhere.Electronic mail messages may also be composed and received in a similarmanner in step 3635.

Different types of communication may be provided as appropriate. Forexample, voice communications may be provided in step 3640. Textcommunication may be provided in step 3642. Video communication may beprovided in step 3644. Other formats of communication may also besupported if desired.

In step 3650, data may be transmitted by a communications device in oneof the INCs in the MPN. This may include substep 3652 transmitting imagedata, substep 3654 transmitting audio data, substep 3656 transmittingvideo data, and substep 3658 transmitting text data. The data to betransmitted may be provided by the user with a user input INC, may bestored in memory within the MPN, and may be transmitted among INCs inthe MPN prior to sending.

In step 3660, data may be received by a communications device in one ofthe INCs in the MPN. This may include substep 3662 receiving image data,substep 3664 receiving audio data, substep 3666 receiving video data,and substep 3668 receiving text data. The data received may betransmitted among INCs in the MPN and stored in memory within the MPN,prior to its being provided to the user on one or more of the INCs, suchas a display INC or audio output INC. If desired, a communications alertmay be provided to the user on the display or audio output INC to letthe user know that a message has been received.

If desired, input and output INCs in the MPN may be shared between acommunications function and another function of the MPN. For example,music may be paused or muted while voice communications orcommunications alerts are being provided to the audio output INC.

FIG. 37 shows more detail of step 3610 (FIG. 36), communicating betweenMPNs. All steps are optional and may be performed in any suitable order.As described above, one of the INCs of the MPN may include acommunications device for exchanging data with an INC of another MPN.Alternatively, the communications device used for exchanging data amongINCs of a single MPN may also be used to exchange data with another MPNthat may be in proximity. For example, the user may have downloadedsoftware into the control unit or other INC that allows suchcommunication. The user may use the user input INC to notify the MPNthat these communications are to begin. The MPN may then begin to sendmessages to an INC of the other MPN, and may listen for incomingmessages from the other MPN. In this manner, each MPN may determine thenetwork identifier of the other user's MPN. In step 3710 of FIG. 37,data may be sent from one MPN to another. For example, the control unitor other INC may tag an outgoing message with the network identifier ofthe other MPN.

The data may include personal data in step 3720. For example, if the twoMPNs are configured to provide personal organization features, the datasent from one to the other may include contact information, such as aname, phone number, electronic mail address, or other suitableinformation.

In step 3730, the data sent between MPNs may include game data. This mayallow the users to play a game that requires two or more players, ifboth users have the same game software installed.

In step 3740, the data may allow two users to compete athletically. Forexample, the two users may each be on a stationary bicycle, andperformance data may be exchanged between them. The two MPNs maydetermine who wins the competition based on data gathered from the twostationary bicycles or other sensors.

In step 3750, one user may send software to another user. This mayinclude, for example, software that enables an MPN to perform a specificfeature or provide a specific function. In step 3760, one user may beallowed to send a digital music file, or other recorded media, toanother.

Any other suitable type of data may be exchanged between MPNs. Ifdesired, data may be exchanged between more than two MPNssimultaneously, for example allowing a game with more than two players.

FIG. 38 shows two users with MPNs that are communicating. First user3820 is wearing first MPN 3810. First MPN 3810 includes control unit3830 and display INC 3840. User controls may be incorporated into eitherINC. Second user 3870 is wearing second MPN 3860, consisting of controlunit 3880 and display INC 3890. Either of these two INCs may have usercontrols as well. Data may be exchanged between control unit 3830 andcontrol unit 3880. Exchanged data may be displayed on display INC 3840and display INC 3890. User 3820 and user 3870 may, for example, exchangepersonal contact information or may play a game. The INCs shown aremerely illustrative.

Another example of two users with communicating MPNs is shown in FIG.39. First user 3920 is on first bicycle 3915, mounted on a stationarytraining stand. Second user 3970 is on second bicycle 3965, also mountedon a stationary training stand. First MPN 3910 may include INC 3925which may combine display functions and user controls with a controlunit and which may be mounted on bicycle 3915. First MPN 3910 mayinclude audio output INC 3930 worn by first user 3920 inside a helmet orheadband. It may include INC 3935 that controls the difficulty settingof the training stand. It may also include INC 3940 that measures thespeed of the rear wheel of bicycle 3915. Second MPN 3960 may similarlyinclude user input/display/control unit 3975, audio output INC 3980,difficulty setting INC 3985, and speed sensor 3990. The two controlunits may control the difficulty for the two riders to simulate aspecific race course, and may compare the speeds of the two riders. Thedisplay INCs may be used to provide feedback on the comparative progresson the simulated course of the two riders, for example notifying eachrider of the comparative position of the other. The INCs shown aremerely illustrative.

FIG. 40 shows more detail of step 3220 (FIG. 32), providingentertainment functions. All steps are optional and may be performed inany suitable order. In step 4010, recorded music may be played. Forexample, songs may be stored in digital format (e.g., MP3 format) inmemory in the control unit or other INC with storage capabilities. Thestorage INC may read the digital audio data and send it to the audiooutput INC, which may play the audio for the user. If desired, thesystem may provide audio control functions, such as volume control,playing and stopping, skipping songs, repeating a song, random play,etc. In step 4015, broadcast music (e.g., radio) may be played by theMPN. A radio receiver may be included in one of the INCs. The radiosignal may be received and sent to the audio output INC to allow theuser to listen. If desired, the audio signal may be digitized forprocessing within the system. If desired, the system may include volumechanging and station selection functions, and other desiredradio-related features.

In step 4020, the system may allow audio to be recorded. For example,one of the INCs may include a microphone. The audio may be digitized andstored into memory in one of the INCs, such as a control unit. Therecorded audio may be replayed by the user, using the audio output INC.Similarly, video segments may be captured in step 4022 and still videoimages may be captured in step 4024 by an INC with a video input. Thevideo segments may be digitized and stored in memory in one of the INCs.If desired, the captured video segments and images may be viewed by theuser on the display INC.

If desired, any stored music or any recorded media may be shared with auser of another MPN, as described above in conjunction with FIG. 37. Anyrecorded audio, video, or image data may be uploaded to a personalcomputer, if desired.

In step 4030, the user may be allowed to play a game. The game mayinvolve only the user of the MPN. Alternatively it may involve a user ofanother MPN, if one of the INCs in each MPN includes a communicationdevice capable of communicating with the other MPN. For example, thewireless communications device within each of the INCs may be used totransfer game-related information between MPNs if the two users are inclose proximity. An INC of the MPN may also be configured to communicatewith an external game device.

Music and audio cues may both be provided by a single MPN, as describedpreviously in conjunction with FIG. 29.

FIG. 41 shows more details of step 3235 (FIG. 32), providing personalorganization features with an MPN. All steps are optional and may beperformed in any suitable order. In step 4110, the MPN may supportscheduling of appointments. The user input INC and display INC may beused for entering new appointments, modifying appointments, and viewingupcoming schedules. The display INC and audio output INC may be used toinform the user of imminent appointments. In step 4120, the MPN maymanage contact information. This may include names, phone numbers,addresses, electronic mail addresses, and other information aboutcontacts. In step 4130, the MPN may be used to manage a task list. Forexample, the user may be allowed to enter and prioritize tasks, and totrack their completion. In step 4140, the MPN may allow the user to keepa journal. The user may be able to create text, audio, video, and othertypes of entries.

In step 4150, the personal organizer data stored by the MPN may besynchronized with another system, such as a software application runningon a personal computer. Appointments, contacts, tasks, and journalentries created on either system may be copied to the other system. Thismay allow the user to keep a permanent or backup copy of data created inthe mobile system, and may also allow the user to take advantage of thekeyboard, mouse, and full-sized monitor on the personal computer toenter significant amounts of information. In step 4160, information maybe shared with another MPN, as described above in conjunction with FIG.37.

FIG. 42 shows more detail of step 4140 (FIG. 41), allowing the user tomaintain a mobile electronic journal. All steps are optional and may beperformed in any suitable order. In step 4210, a user may be allowed toenter journal entries. Entries may include voice in substep 4212, textin substep 4214, input from an electronic sketchpad in substep 4216, orany other suitable type of entry or combination of entries. In step4220, the user may be allowed to capture a video image, for exampleusing an INC that has digital camera hardware. If desired, the user maycapture a video clip. In substep 4225, the captured video image may bestored with a journal entry. For example, it may be stored in the samememory, and there may be a link from one to the other. In step 4230, thejournal entry may be automatically tagged with the current date and timeif one of the INCs in the MPN includes a clock. In step 4235, thejournal entry may be automatically tagged with the current location, ifone of the INCs in the MPN includes a position monitor such as a globalpositioning system (GPS) monitor. In step 4240, the user may be allowedto control functions of the journal using the audio input, if the MPNincludes a speech recognition function. In step 4250, a database may bedownloaded into memory in the MPN. The database may include data ofinterest to the user, and may relate to topics to which the user mayrefer in the journal. For example, the database may includetravel-related information, music-related information, school-relatedinformation, work-related information, or any other suitable data. Instep 4255, the user may be allowed to link a journal entry to a databaseelement.

In step 4260, any journal entries stored in the MPN may be uploaded to apersonal computer. This may include the voice, text, and drawing partsof the entries, as well as any linked images and time and location tags.It may also include links to any database elements that may be linked tothe journal entries, or it may include the data from the databaseelements themselves. In step 4265, the uploaded journal may be convertedinto a standard file format, so that it may be easily viewed or printedwith the personal computer. The file format may include HTML, PDF, orany other suitable format. Images and audio segments may also be storedin a common file format. The data may be loaded into a database on thepersonal computer if desired.

FIG. 43A shows more detail of step 3208 (FIG. 32), providing a guidancefunction using an MPN. In step 4310, the MPN may include a positionmonitor INC. This may be a GPS monitor in substep 4312. The system mayalso include an elevation monitor in substep 4314, which may, forexample, use barometric pressure readings. In step 4320, the positionmonitor may be used to provide current user information. This mayinclude current position in substep 4322, current speed in substep 4324,current elevation in substep 4326, and current elevation gain in substep4328. If desired, the system may also collect direction information, forexample from a compass, and provide direction information.

In step 4330, route guidance may be provided to a user. Turning to FIG.43B for greater detail of step 4330, route guidance may include step4331, in which map information may be downloaded into memory in the MPN.The map information may be downloaded using the wireless communicationsdevice in one of the INCs. Alternatively, it may be loaded from a memorydevice, such as a CD-ROM. In step 4332, the user may be allowed to entera desired location. For example, the user may enter an address or thename of a destination, the user may choose a destination from a list,the user may point to a destination on a map displayed on a touchscreen, or the user may speak the desired location. In step 4333, an INCin the MPN may calculate a route from the current location to thedesired location. This may be done using any suitable algorithm orcombination of algorithms that may compare various routes based ondistance, estimated time, traffic, road conditions, or any othersuitable criteria. If desired, the user may be allowed to enter criteriafor choosing a route, or may be allowed to choose from multiple routes.In step 4334, map information may be displayed. The map information mayinclude the current location, the desired location, and/or all or partof the route between them. In step 4335, the user's current location maybe displayed on the map. This may also include other information, suchas the user's direction and speed. In step 4336, route guidance may bedisplayed. In addition to displaying the chosen route on the map, thesystem may provide, either visually or audibly, prompts informing theuser of turns and other actions. The system may also make corrections tothe route if the user misses a turn or otherwise does not follow theguidance.

Returning to FIG. 43A, in step 4340, the system may collect and storeposition information as the user moves. This may include, for example,location, speed, and elevation, along with the time at which eachmeasurement was taken. This step may also include substep 4341,uploading the collected data to a base station or personal computer. Thecollected data may be saved in a database, displayed, or analyzed, by anINC of the MPN, by a base station, by a personal computer, by a computeraccessed over a wide area network such as the Internet, or in any othersuitable location. In step 4342, the user may be allowed to annotate thecollected position data, or otherwise modify it. For example, the usermay enter text, create a voice annotation, or capture a video image orsegment. Annotations may include information about a location, about theroute, personal notes, images or video clips of sights seen, or anyother information. If desired, the system may have a number ofpredefined annotations that may be quickly and easily entered by theuser at any point. The system may store the annotation with the positioninformation, and may create a link between the data items. The user mayalso be allowed to modify the collected data itself. The annotation ormodification may be created as the position information is collected insubstep 4343, for example using an input device that may be an INC inthe MPN. The annotation or modification may also be created after theposition information has been collected in substep 4344, for exampleusing an input device connected to a personal computer. In step 4345,the collected information may be correlated with map data. This may bedone in the MPN, using map data stored in memory in an INC of the MPN,or on a personal computer after the position information has beenuploaded. The position information, along with any annotations, may bedisplayed on a map, for example showing the route taken by the user.

In step 4350, position information may be correlated with simultaneouslycollected performance information. This may be useful in an MPN that isalso used to support athletic workouts. For example, the route may be anathletic training route or an athletic competition route. Theperformance information may, for example, be speed in substep 4351,heart rate in substep 4352, cadence, or any other suitable performancedata. The personal data may be stored with the position data, and thesystem may also store links between the two data items. This collectedperformance data may be displayed during the session. It may also bedisplayed or printed on a personal computer at a later time. It may bedisplayed in a table, in a graph, on a map, on an elevation profile, orany other suitable format. In step 4353, performance data may becollected during multiple sessions. In step 4354, the performance datamay be compared between sessions. The comparison may be for the entiresessions, or for portions of the sessions following the same route. Forexample, a table or graph may be used to show the performancedifferences between two sessions. Summary information, such as averages,may also be provided. Information may be displayed on an INC of the MPN,on a personal computer after being uploaded, to a computer accessed viaa wide area network such as the Internet, or at any other suitablelocation.

The collected position information may be used to recommend a route fora later session in step 4360. For example, the MPN may store positioninformation from one or more sessions, and may construct map data ofroutes that are available to the user. Prior to or during a latersession, the constructed map data may be used to plan a route for theuser. The system may also use the collected performance data to plan theroute. If desired, the route may be that of an upcoming athleticcompetition, and the system may be used to collect information about theroute, such as elevation profile, distance of individual segments,landmarks, or other information of interest. In substep 4361, a routemay be recommended based on a desired workout intensity. For example,the system may use collected heart rate data or an elevation profile tochoose a route with the desired difficulty. In substep 4362, a user mayspecify a desired elevation profile, and the system may choose a routethat most closely matches the user's preference. In substep 4363, thesystem may recommend a route based on a desired distance chosen by theuser. If desired, the system may allow the user to specify any othersuitable criteria, or combination of criteria, for route selection. Instep 4365, the MPN may provide directions or other guidance to the userduring a session, based on the selected route. If desired, the guidancemay be based on a route chosen ahead of time and downloaded.Alternatively, the directions may be made dynamically, as specificdecision points are reached. For example, a prompt to take a specificturn may be shown on the display INC or played through the audio outputINC. The system may also make modifications to the recommended route ifthe user does not follow the prompts. If desired, the chosen route maybe based on map and elevation information loaded from a CD-ROM or othermemory device or loaded from the Internet or other network, rather thanusing position information collected by the user.

Position data collected in one session may also be used to simulate thesame route in a later session. For example, a user may travel the routeof an upcoming competition in one or more sessions and collect positionand elevation information. This collected position and elevationinformation may be used to control exercise equipment in later sessionsto simulate the racecourse.

FIG. 44 shows an illustrative MPN 4400 that may be used to provideguidance to an athlete. INC 4410 may be worn on a waistband, and mayinclude a control unit, a GPS monitor, an elevation sensor, user inputcontrols, and a clock. INC 4420 may be worn on a wristband and mayinclude a display device and an accelerometer. INC 4430 may be worn on aheadband, and may include an audio output device. INC 4440 may be wornon a chest strap and may include a heart rate sensor. INC 4450 may beworn on an ankle band and may include an accelerometer. Use ofaccelerometers mounted on the arm and leg to perform functions such asmeasuring cadence and providing form feedback is described in moredetail below. INCs shown are merely illustrative, and all INCs areoptional.

FIGS. 45A through 45L show examples of screens that may be provided bydisplay INC 4420 in an MPN 4400 (FIG. 44) that may be used for guidanceand athletic functions. FIG. 45A provides a display of the user'scurrent altitude. FIG. 45B provides a display of the user's currentgeographical location. FIG. 45C provides a display of the user's currentspeed. FIG. 45D provides a display of the user's current rate ofelevation change. FIG. 45E provides a display of the user's heart rate.FIG. 45F provides a display of a route prompt. FIG. 45G provides adisplay of the user's current cadence. FIG. 45H provides a display ofthe user's current stride length. FIG. 45I provides a display of thecurrent date and time. FIG. 45J provides a display of a session totaltime and partial time from a stopwatch function. FIG. 45K provides adisplay of an interval timer. FIG. 45L provides a display of a speedprompt. These screens are merely illustrative. Any suitable informationmay be displayed, in any suitable format. If desired, any of thisinformation may be sent to an audio output INC in addition to or insteadof the display INC.

FIGS. 46 through 49 show illustrative screens that may be displayed on apersonal computer configured to interface with an MPN that providesguidance features and athletic features. FIG. 46 shows session overviewscreen 4600 that may display collected position, performance, andannotation data for a session. Graphs 4610, 4620, 4630, 4640, and 4650,along with note line 4660, may all be displayed relative to a commontime line. Graph 4610 may display elevation vs. time for the session orportion of session. Graph 4620 may display speed vs. time for thesession or portion of session. Graph 4630 may display heart rate vs.time for the session or portion of session. Graph 4640 may displaystride length vs. time for the session or portion of session. Graph 4650may display cadence vs. time for the session or portion of session. Theuser may be allowed to click on any graph to view more details of thegraphed data (such as a chart of the data). These graphs are merelyillustrative. Any suitable data may be graphed or charted. Note line4660 may display indicator to show the link between time and eachannotation. For example, indicator 4662 may indicate that an audioannotation has been linked to that first specific time during thesession. Indicator 4664 may indicate that a video annotation may belinked to that second specific time during the session. Indicator 4666may indicate that a text annotation has been linked to that thirdspecific time during the session. The user may be allowed to point themouse at an indicator or click on it to view the actual annotation. Menubar 4670 may provide user access to various functions. For example, filemenu 4672 may allow the user to save the session data, open a file withother session data, or perform other file related functions. Notes menu4674 may allow the user to perform functions related to annotations,such as adding a new annotation, modifying an annotation, deleting anannotation, or viewing an existing annotation. Time menu 4676 may allowthe user to perform time-related functions, such as modifying which timespan from the session is graphed. View menu 4678 may allow the user tochange the display to another view of the same data (such as a chart),or to any other display supported by the system. This may include, forexample, allowing the user to select session comparison display 4700 ofFIG. 47 or map view 4800 of FIG. 48. The menu options described here aremerely illustrative. Any suitable menu options may be offered. Forexample, an option may be offered to allow the user to select whichtypes of data to graph.

FIG. 47 shows session comparison screen 4700 that may display collectedposition, performance, and annotation data for multiple sessions orpartial session in which the user followed the same route. Graphs 4720,4730, and 4740 may all be displayed relative to a common distance line.Graph 4720 may display elevation vs. distance for the common route orportion of route. Graph 4730 may display speed vs. distance for thefirst session or portion of session on date 4735. Graph 4740 may displayspeed vs. distance for the second session or portion of session on date4745. The user may be allowed to click on any graph to view more detailsof the graphed data (such as a chart of the data). These graphs aremerely illustrative. Any suitable data may be graphed or charted.Summary region 4750 may display and compare summary data from themultiple sessions. For example, if speed data is graphed on the screen,the summary region 4750 may display average and maximum speed for thegraphed segment of each session. Menu bar 4710 may provide user accessto various functions. For example, file menu 4712 may allow the user tosave the session data, open a file with other session data, or performother file related functions. Time menu 4714 may allow the user toperform time-related functions, such as modifying which time span fromthe session is graphed. Data menu 4716 may allow the user to performdata-related functions, such as modifying which data from the session isgraphed. View menu 4718 may allow the user to change the display toanother view of the same data (such as a chart), or to any other displaysupported by the system. This may include, for example, allowing theuser to select session overview display 4600 of FIG. 46 or map view 4800of FIG. 48. The menu options described here are merely illustrative. Anysuitable menu options may be offered. For example, an option may beoffered to view or modify annotations.

FIG. 48 shows map view screen 4800 that may display collected position,performance, and annotation data for a session or partial session inrelation to a map. Date field 4820 may display the date and/or time ofthe session being viewed. Road indicator 4830 may show the roads,trails, and other fixed items from the region in which the sessionoccurred. Route indicator 4840 may be used to indicate the actual routefollowed by the user during the session. Route indicator 4840 may havedifferent characteristics to indicate different performance data. Forexample, there may be three different line styles used to indicate heartrate above a desired zone, within a desired zone, and below a desiredzone. The number of line styles and the performance parameter shown aremerely illustrative. Any suitable data divided into any suitable numberof zones may be drawn on the map. If desired, multiple performanceparameters may be shown on the same map. The user may be allowed toclick on the map to view more details of the data (such as a chart orgraph of the data). Note indicators may be displayed on the map to showthe link between the route and each annotation. For example, indicator4852 may indicate that an audio annotation has been linked to that firstspecific time during the session. Indicator 4854 may indicate that avideo annotation may be linked to that second specific time during thesession. Indicator 4856 may indicate that a text annotation has beenlinked to that third specific time during the session. The user may beallowed to point the mouse at an indicator or click on it to view theactual annotation. Legend 4860 may display a legend of the line stylesused for the road indicator and route indicator, along with any otherinformation that may be displayed on the map. For example, a legend maybe provided for the different styles of annotation indicator. Menu bar4810 may provide user access to various functions. For example, filemenu 4812 may allow the user to save the session data, open a file withother session data, or perform other file related functions. Notes menu4814 may allow the user to perform functions related to annotations,such as adding a new annotation, modifying an annotation, deleting anannotation, or viewing an existing annotation. Data menu 4816 may allowthe user to perform data-related functions, such as modifying which datafrom the session is shown on the map. View menu 4818 may allow the userto change the display to another view of the same data (such as achart), or to any other display supported by the system. This mayinclude, for example, allowing the user to select session overviewdisplay 4600 of FIG. 46 or session comparison display 4700 of FIG. 47.The menu options described here are merely illustrative. Any suitablemenu options may be offered. For example, an option may be offered tozoom into a portion of the route.

FIG. 49 shows session planning screen 4900 that may allow the user toenter desired attributes of an upcoming session, to allow the system toplan an appropriate route. For example, the user may be allowed to entera desired total distance in screen region 4910. Screen region 4920 mayallow the user to enter a desired total time for the session. Screenregion 4930 may allow the user to enter a desired elevation gain for theroute. Screen region 4940 may allow the user to enter a desired pace orspeed for the session. Screen region 4950 may allow the user to enter adesired heart rate or heart rate range for the session. These parametersare merely illustrative. Any suitable parameters may be offered. Theuser may be allowed to enter a subset of desired parameters, and thesystem may create a route that best matches the entered parameters. Menubar 4960 may provide user access to various functions. For example, filemenu 4962 may allow the user to save the session data, open a file withother session data, or perform other file related functions. Maps menu4964 may allow the user to perform functions related to maps, such asviewing maps of available routes, and selecting one or more preferredroutes. The menu options described here are merely illustrative. Anysuitable menu options may be offered. For example, an option may beoffered to view data from previous sessions.

FIG. 50 shows more detail of step 3210 of FIG. 32, providing an athleticfunction with an MPN. All steps are optional and may be performed in anysuitable order. In step 5005, the MPN may be used to control a workout.In step 5010, the MPN may be used to control one or more sections of aworkout. In step 5015, the MPN may be used to collect data from aworkout. In step 5020, the MPN may be used to provide both music andaudio workout cues, as described previously with respect to FIG. 29. Instep 5025, the MPN may be used to provide route guidance during aworkout, as described previously with respect to FIG. 43A. In step 5030,the MPN may measure an athlete's cadence. In step 5035, the MPN maymeasure an athlete's stride length. In step 5040, the MPN may be used tocontrol a piece of exercise equipment, as described previously withrespect to FIG. 21. In step 5045, the MPN may be used to collect datafrom a piece of exercise equipment, as described previously with respectto FIG. 21. In step 5050, the MPN may correct errors in collectedathletic data. In step 5055, the MPN may remind an athlete to consume aconsumable. In step 5060, the MPN may use previously stored data toestimate a performance parameter. In step 5065, the MPN may provide foran athletic competition between two or more athletes, as describedpreviously with respect to FIG. 39. In step 5070, the MPN may providefor a coaching interface. In step 5075, the MPN may count swimming laps.In step 5080, the MPN may provide form feedback to an athlete. In step5085, the MPN may provide a training journal. More details of theseembodiments are described below. These athletic uses of the MPN aremerely illustrative. Other athletic uses are possible if desired.

FIG. 51 shows flow chart 5100 of an illustrative process for providingworkout control and feedback. All steps are optional and may beperformed in any suitable order. In step 5110, workout parameters may bedefined. The parameters may be defined, for example, on a coach'scomputer or on an athlete's computer. The parameters may be entered by auser such as the coach or athlete, or they may be generatedautomatically by a coaching software application. The parameters maydefine aspects of a planned workout, such as its type, duration,intensity, etc. In step 5120, if the workout parameters were defined ona coach's computer, they may be downloaded to the athlete's computer. Instep 5125, the parameters may be downloaded from the athlete's computerto an INC in the MPN, such as a control unit. In step 5130, the INC maycontrol aspects of the workout session, using an output INC in the MPN.In step 5140, the INC may collect workout results from an input INC inthe MPN. In step 5150, the workout results may be uploaded to theathlete's computer. In step 5155, the workout results may be uploaded tothe coach's computer. In step 5160, the workout results may be stored,for example on the athlete's computer or the coach's computer. In step5170, the workout results may be analyzed, for example on the athlete'scomputer or the coach's computer. For example, the workout results maybe displayed, or may be compared with workout results from other workoutsessions. In step 5180, the workout results may be used to determineparameters for one or more upcoming workout sessions, for example on theathlete's computer or the coach's computer.

FIG. 52 shows a block diagram of an illustrative system 5200 forcommunicating between a personal computer 5210 and a control unit 5240that is an INC in an MPN. Personal computer 5210 may have communicationsdevice 5220, control unit 5240 may have communications device 5250, andthey may communicate using communication path 5230. Communication path5230 may be a wireless radio frequency link, an infrared link, a dockingstation link, a USB link, a serial port link, or any other suitable typeof communications path. Control unit 5240 may include processor 5260 forexecuting software related to controlling a workout, collecting workoutresults, communicating with personal computer 5210, and communicatingwith other INCs in the MPN. Control unit 5240 may also include memory5270 for holding software, downloaded workout parameters, and collectedworkout results.

FIG. 53 shows a block diagram of an illustrative MPN 5300 forcontrolling aspects of an athletic workout and collecting results from aworkout. Control unit 5240 may be the same control unit shown in FIG.52, and may be configured to communicate with a personal computer asshown in that FIG. It may also have wireless communications device 5310for communicating with other INCs in MPN 5300 over wirelesscommunication path 5350, such as data collection INC 5320 and output INC5330. If desired, wireless communications device 5310 may be the same ascommunications device 5250. If desired, control unit 5240 may beomitted, and its functions may be assumed by other INCs in the MPN.

Data collection INC 5320 may have wireless communication device 5322 forsending collected data to control unit 5240 or other INC having storagecapabilities. It may also have data collection circuit 5324. Datacollection circuit 5324 may collect any athletic data, such as speed,heart rate, power, resistance, location, cadence, or any other suitabletype of athletic data. Data collection INC 5320 may be worn by theathlete. If desired, data collection INC 5320 may be mounted on a pieceof athletic equipment or a bicycle and may collect data from thatequipment.

Output INC 5330 may have wireless communication device 5332 forreceiving control commands from control unit 5240 or other suitable INC.It may also have output circuit 5334. Output circuit 5334 may outputathletic control data using any appropriate method, such as displaying aprompt to the user, outputting a prompt to the user, controllingresistance, controlling speed, or any other suitable type of athleticcontrol. Output INC 5330 may be worn by the athlete. If desired, outputINC 5330 may be mounted on a piece of athletic equipment or a bicycleand may send control commands to that equipment.

FIG. 54 shows how MPN 5300 (FIG. 53) may communicate with an athlete'spersonal computer 5210 and a coach's personal computer 5410. Athlete'spersonal computer 5210 may communicate with coach's personal computer5410 using any suitable network 5415, such as the Internet. Eithercomputer may connect with network 5415 using connection 5412 and 5418,such as a telephone modem, a cable modem, a digital subscriber linemodem, or any other suitable type of connection. As shown previously,athlete's personal computer 5210 may connect to control unit 5240, andcontrol unit 5240 may send commands to athletic output INC 5330 andcollect data from athletic data collection INC 5320. If desired,connections may not all be in place simultaneously. For example, at afirst time, coach's computer 5410 may be connected to network 5415, andworkout parameters may be uploaded to a web server. At a second time,athlete's computer 5210 may be connected to network 5415, and workoutparameters may be downloaded from the web server. At a third time,athlete's personal computer 5210 may be connected to control unit 5240,and workout parameters may be downloaded into control unit 5240. At afourth time, which may be during a workout session, the control unit5240 may send control commands to athletic output INC 5330 and mayreceive data from athletic data collection INC 5320. At a fifth time,workout results may be uploaded from control unit 5240 to athlete'spersonal computer 5210. At a sixth time, workout results may be uploadedfrom athlete's personal computer 5210 to a web server in network 5415.At a seventh time, workout results may be downloaded from the web serverin network 5415 into coach's computer 5410. If desired, data may be sentdirectly between coach's computer 5410 and athlete's computer 5210,rather than using a web server to store data sent from one to the other.If desired, control unit 5240 may be omitted, and athlete's personalcomputer 5210 may connect directly to athletic output INC 5330 andathletic data collection INC 5320 or storage INC (not shown).

FIG. 55 shows illustrative MPN 5500 that may be used to provide controlof an athletic workout and collect workout results. INC 5510 may be acontrol unit, and may be worn by the athlete. INC 5515 may be anathletic data collection INC worn by the athlete, and may include aheart rate sensor. INC 5520 may be an athletic output INC worn by theathlete, and may include an audio output INC. INC 5525 may be anathletic output INC mounted on a bicycle, and may include a display INC.INC 5530 may be an athletic data collection INC mounted on a bicycle,and may include a pedal cadence sensor. INC 5535 may be an athletic datacollection INC mounted on a bicycle, and may include a wheel speedsensor. INC 5540 may be an athletic output INC mounted on a bicycletraining stand, and may include resistance control device. During aworkout, the control unit may control aspects of the workout by changingthe cycling difficulty using INC 5540, and by providing prompts to theathlete using INC 5520 and INC 5525. Prompts may include, for example,prompts to pedal faster, slower, harder, or easier, to stand or sit, topedal with one leg or both legs, or any other suitable prompts. INCsshown are merely illustrative, and each INC is optional.

FIG. 56 shows a flow chart of an illustrative process 5600 for managinga workout plan. All steps are optional and may be performed in anysuitable order. The workout plan may be managed using software onathlete's computer 5210 or coach's computer 5410 (FIG. 54). In step5610, a workout goal may be defined. This may include a specific date insubstep 5612, a specific upcoming competition in substep 5614, aspecific performance goal in substep 5616, a specific health goal insubstep 5618, or any other suitable type of goal. If desired, multiplegoals may be defined. In step 5620, a workout plan may be defined basedon the workout goal. This may include different types of workouts,different periods of time with specific sub-goals, or other suitableplan. In step 5625, a workout session may be defined. That may include atype of workout, duration, intensity, repetitions, or any other suitableparameters. As many parameters as desired may be created for eachworkout. The workout plan may include tracking of multiple plannedworkout sessions. In step 5630, the workout parameters may be downloadedfrom the coach's computer or athlete's computer into an INC of the MPN,such as a control unit or storage INC. In step 5635 and step 5640,during a workout session, aspects of the workout may be controlled anddata may be collected. In step 5645, workout results may be uploaded.This may include storing results on the athlete's computer or thecoach's computer. Results may be stored for multiple workout sessions.This may include storing the parameters that were used to define theworkout sessions, as well as data collected during the sessions. In step5650, workout results may be displayed for the athlete or coach. In step5655, workout results may be analyzed. This may include comparingresults between multiple workout sessions. In step 5660, the workoutresults may be used to modify one or more parameters for an upcomingworkout session. Workout results may include data collected during aworkout, as well as the workout parameters used during the workoutsession. Workout results may include information on missed workoutsessions. Workout results may also include related information such asathlete health information, athlete eating and drinking records,athlete's resting heart rate, and other auxiliary information. Forexample, a future workout may be made easier or harder depending on theresults of the workout. In another example, if the time of a workoutsession was changed, an upcoming session may also be moved or canceled.If desired, in substep 5665, rules may be applied to restrict how futureworkout modifications may be made. For example, a rule may restrict thesystem from scheduling two workouts of the same type on the same orconsecutive days. As another example, the intensity, difficulty, orduration may not be allowed to increase more than a fixed percentage,such as ten percent. And in step 5670, the results of all workouts in aplan may be tracked as they occur. The coach or athlete may be allowedto view historical data, to view trends and improvements, or compare theresults of two or more workout sessions. This may also include comparingthe collected workout results to the workout plan goal or goals. Ifdesired, other data, such as data entered by the coach or athlete, maybe compared with the workout plan goal.

In FIG. 57, more details are shown of step 5625 (FIG. 56), defining theworkout parameters. All steps are optional and may be performed in anysuitable order. In step 5710, the day and time of a workout may bedefined. The workout time may be defined with any suitable degree ofspecificity, such as any time within a week, any time within a three dayperiod, any time on a specific day, before or after a different workout,or at a specific hour. In step 5720, the type of workout may be defined.This may include a general workout type, such as running, cycling,swimming, weightlifting, rowing, or the like. It may also include astyle of workout, such as endurance, speed work, interval training,fartlek (“speed play”—bursts of speed during a training run) training,hill work, strength training, or any other suitable style. In step 5730,the duration of the workout may be defined. The duration may be measuredin time, distance, or any other suitable units. The duration may beexpressed as a range, if desired.

In step 5740, the workout may be divided into sections. Each section mayhave its own goal, such as warm up, increasing anaerobic threshold,recovery, increasing endurance, cool down, or any other suitable goal.Each section may be provided its own set of workout parameters. Forexample, in step 5750, target intensity may be defined for a section. Instep 5760, target heart rate, speed, power, cadence, or any otherparameter to be controlled may be defined for the section. If desired,multiple parameters to be controlled may be defined. If desired, thedesired profile of the parameter or parameters during the section may bespecified. If desired, a section may be defined with no parameter to becontrolled. For example, the desired heart rate for a section may be 100beats per minute at the start of the section, and may increase linearlyto a value of 130 beats per minute at the end of the section. In step5770, the duration of each section may be defined. The duration may bemeasured in units of time, units of distance, or any other suitableunits. In step 5780, the controlling parameter for the section may bedefined. For example, to control the heart rate, the athlete's speed maybe controlled by sending audible prompts, the speed may be controlled bysending commands to a piece of exercise equipment, or the resistance maybe controlled by sending commands to a piece of exercise equipment. Ifdesired, multiple controlling parameters may be specified. If desired,limits on the values or rate of change of the controlling parameter maybe specified. In step 5790, repetitions of sections may be defined. Forexample, two sections may be alternated, and the combination may berepeated four times. Any other suitable attributes of a section may alsobe defined. If desired, the definition of one section may be copied fromthe definition of another section.

FIG. 58 shows illustrative screen 5800 that may be shown on athlete'scomputer or coach's computer for defining a workout. Region 5810 may beused to enter the total number of sections. Region 5820 may be used toenter the duration of a section, in this example in minutes. Selection5830 may be used to choose the parameter to be controlled. In thisexample, heart rate has been chosen, and other choices are cadence,power, and speed. The user may also choose to control no parameterduring the section. Selection 5840 may allow the user to specify thetype of control, such as constant, between two values, linear, or on adefined curve. In this example, the user has chosen linear control. Inregion 5850, the user may enter the value or values at which to controlthe parameter. In this example, the user has entered a desired startingand ending heart rate for the section. Selection 5860 may allow the userto specify the controlling parameter, such as controlling heart rate bycontrolling speed or difficulty. In this example, the user has chosendifficulty as the controlling parameter. Scroll bar 5880 may allow theuser to view and modify more fields, such as parameters for othersections in the workout. Menu bar 5870 may allow the user to accessother features, such as file features (e.g., save and loading workoutsession definition files), edit features, download features (e.g.,downloading workout definitions from a coach's computer or to an INC ofthe MPN), and help features.

FIG. 59 shows illustrative data structure 5900 that may be used to storeinformation about a workout session. This data structure or a similarstructure may be stored in a personal computer, in memory in an INC ofthe MPN, or in any other suitable location. If desired, similarinformation may be stored in multiple data structures. A workout sessionmay consist of multiple “super sections,” wherein each super sectionconsists of one or more sections, and wherein each super section may berepeated multiple times. Data structure 5900 may include a definition ofthe number of super sections 5910. It may also include the definition ofeach super section, such as super section definition 5920, super sectiondefinition 5940, and super section definition 5960. Each super sectiondefinition may include a definition of number of sections in the supersection, such as definition 5921, definition 5941, and definition 5961.Each super section definition may include a definition of number oftimes the super section is to be repeated during the workout session,such as definition 5922, definition 5942, and definition 5962.

Section A definition 5925 may specify that the section is to have aduration of 15 minutes in duration definition 5926. It may specify thatthe heart rate is to be controlled in primary parameter definition 5927,and that the heart rate is to follow a linear curve from 100 beats perminute to 125 beats per minute in curve definition 5928. It may specifya secondary parameter of cadence, which is to be kept at a rate of 90revolutions per minute in secondary parameter specification 5929. It mayspecify in controlling parameter definition 5930 that the heart rate isto be controlled by user audio prompt. In this definition, section A isto occur once during the workout session.

Section B definition 5945 may specify that the section is to have aduration of 5 minutes in duration definition 5946. It may specify thatthe heart rate is to be controlled in primary parameter definition 5947,and that the heart rate is to be maintained in a range between 150 beatsper minute and 160 beats per minute in curve definition 5948. It mayspecify a secondary parameter of cadence, which is to be kept at a rateof 90 revolutions per minute in secondary parameter specification 5949.It may specify in controlling parameter definition 5950 that the heartrate is to be controlled using a resistance setting output.

Section C definition 5955 may specify that the section is to have aduration of 1 minute and 30 seconds in duration definition 5956. It mayspecify that speed is to be controlled in primary parameter definition5957, and that the speed is to be maintained below 15 miles per hour incurve definition 5958. It may specify a secondary parameter ofresistance, which is to be kept at the easy setting in secondaryparameter specification 5959. It may specify in controlling parameterdefinition 5960 that the speed is to be controlled by user audio prompt.In this definition, section B and section C are combined into a singlesuper section, which is to occur twice during the workout session.

Section D definition 5975 may specify that the section is to have aduration of 15 minutes in duration definition 5976. It may specify thatthe heart rate is to be controlled in primary parameter definition 5977,and that the heart rate is to be maintained at a constant rate of 110beats per minute in curve definition 5978. It may specify a secondaryparameter of cadence, which is to be kept at a rate of 90 revolutionsper minute in secondary parameter specification 5979. It may specify incontrolling parameter definition 5980 that the heart rate is to becontrolled by user audio prompt. In this definition, section D is tooccur once during the workout session.

FIG. 60 shows flow chart 6000 of an illustrative process for controllingmultiple sections of a workout. All steps are optional and may beperformed in any suitable order. In step 6010, an athletic workoutsession may be defined as multiple sections. This workout definition mayoccur, for example, on an athlete's computer or on a coach's computer.In substep 6012, the definition may specify that a section is to berepeated multiple times during a workout session. The repetitions do nothave to be consecutive. In substep 6014, groups of sections, such assuper sections, may be repeated multiple times. In substep 6016, onesection may be a copy of another section, in the same workout or inanother workout. In substep 6018, one section may be a variation ofanother section, in the same workout or another workout. In substep6020, the starting value of a parameter in one sections may be specifiedas the ending value of the same parameter in the previous section.

In step 6030, the workout parameters for each section may be defined.This may include substep 6032 in which a performance parameter to becontrolled may be specified. This may include, for example, heart rate,cadence, power, or speed. In substep 6034, the desired value, values, orprofile of the performance parameter to be controlled may be specified.This may include specifying a constant level, a defined curve, the endpoints of a linear variation, or two values to maintain the parameterbetween. If desired, a range above and below the desired curve may bedefined. In substep 6036, an output parameter to be used to control theperformance parameter may be specified. In substep 6038, one or moresecondary performance parameters with corresponding desired values maybe specified. In substep 6040, the duration of the section may bespecified, for example, in time or distance. After all workoutparameters have been defined, they may be downloaded from the coach'scomputer or athlete's computer into memory in an INC of the MPN, such asa control unit, for use during the workout. If desired, the workoutparameters may be transmitted directly from the coach's computer into anINC of the MPN, or they may be transmitted over a wide area network suchas the Internet to the athlete's computer, and downloaded from theathlete's computer into an INC of the MPN.

In step 6050, data may be collected during the section of the workoutsession. That may include heart rate data in substep 6052, speed data insubstep 6054, position data in substep 6056, cadence data in substep6058, power data in substep 6060, data from a sensor mounted on a pieceof exercise equipment in substep 6062, data from a sensor mounted on abicycle in substep 6064, or any other suitable type of input data. Datacollected during a workout may be presented to the athlete during theworkout, for example on a display INC. If desired, collected data may beuploaded to a base station, the athlete's personal computer or thecoach's personal computer, where they may be stored, displayed as achart or graph, compared with results from previous workouts, orotherwise analyzed. If desired, collected workout results may be used tomodify workout parameters of future workout sessions.

In step 6070, a performance parameter may be controlled during thesection of the workout session. This may be done by prompting the userin substep 6072. The prompt may be a visual prompt in substep 6074 or anaudible prompt in substep 6076. In substep 6078, the prompt may be tochange speed, change intensity or level of effort, change route, or anyother suitable prompt. In substep 6080, the control may be performed bychanging a setting, such as a difficulty, speed, or resistance setting,on an output INC. In substep 6082, the control may be performed bychanging a setting on a piece of exercise equipment.

In substep 6084, the control may be performed using aposition-integral-derivative (PID) servo algorithm, in which the valueof an input parameter, the rate of change of the input parameter, andprevious values of the input parameter are used to calculate a new valuefor the controlling parameter. The system may also include a set oflimits on the output value to prevent it from exceeding a minimum value,a maximum value, and/or a maximum rate of change. In substep 6086, theinput data used in the algorithm may be data that was collected in step6050, and the definition of the input parameter and the controllingparameter may be part of the workout parameters that were defined instep 6030. The constants in the servo equation may be standard values,may be entered or downloaded by a user, or may be derived and modifiedwith use.

In substep 6088, one or more additional parameters may be controlledduring the workout section, as specified in the workout parameters. Forexample, a secondary parameter may be maintained between two values insubstep 6090, maintained at a constant level, controlled linearly, orcontrolled in any other suitable fashion.

In addition to directly collecting data to measure a performanceparameter, an MPN may use stored information along with collectedinformation to estimate a derived performance parameter. A process fordoing so is illustrated in flow chart 6100 of FIG. 61. All steps areoptional and may be performed in any suitable order. In step 6110,previously collected personal data may be stored in an INC of the MPN.The personal data may be age in substep 6112, gender in substep 6114,weight in substep 6116, resting heart rate in substep 6118, maximumheart rate in substep 6120, VO₂ max in substep 6122, results (e.g., timeand distance or speed and distance) from a previous athletic effort insubstep 6124, or any other suitable personal data. The personal data mayhave been collected using an INC of the MPN, in step 6130.Alternatively, the personal data may have been downloaded in step 6135,for example from an athlete's computer or from a coach's computer, whereit may have been entered.

In step 6140, primary performance data may be collected, for example byan INC of the MPN during an athletic effort. The data may be a singlesample, or it may be many samples collected over a period of time. Instep 6150, a secondary performance parameter may be estimated using thestored personal data and the collected primary performance data. Insubstep 6162, maximum heart rate (MHR) may be calculated. MHR is themaximum rate at which the athlete's heart can beat during a maximaleffort, and is commonly measured in beats per minute. The MHR value maybe entered by the user as personal data. The MHR may be estimated by thesystem based on the age and gender entered by the user. For example, MHRis commonly estimated as 220-age in years. Alternatively it may beestimated as 214−(age*0.8) for males and 209−(age*0.7) for females.Another method of estimating MHR is 210−(0.5*age)−(0.05*weight inpounds)+(4 if male or 0 if female). The estimate may be modified basedon the specific type of activity or other factors. Alternatively, MHRmay be estimated based on actual heart rate measurements in a definedathletic effort.

Resting heart rate (RHR) may be entered by the athlete as personal dataor it may be measured. RHR is a measure of the rate at which theathlete's heart beats when at complete rest, and is also measured inbeats per minute. RHR may be estimated based on actual heart ratemeasurements taken over a period of time, for example while the athleteis asleep. Regardless of how MHR was entered, measured or estimated, thepercent of maximum heart rate may be estimated by dividing actual heartrate (HR) by MHR, in substep 6154. Percent of heart rate reserve may beestimated as (HR−RHR)/(MHR−RHR), in substep 6156.

Another performance parameter of interest to athletes is oxygen uptake(VO₂) and maximum oxygen uptake (VO₂ max). VO₂ is a measure of theamount of oxygen removed from the blood and used by the muscles duringan athletic effort. VO₂ max is a measure of the maximum amount of oxygenthat can be used by the athlete during an effort. Both are commonlymeasured in units of ml/kg/min. Although the actual measurement of VO₂requires sophisticated equipment, there are several known methods toestimate it. For example, in “Jack Daniels, Conditioning for DistanceRunning—The Scientific Aspects,” Wiley & Sons, 1978, the followingformulas are used:Percent max=0.8+0.1894393*e(−0.012778*t)+0.2989558*e(−0.1932605*t)VO₂=−4.60+0.182258*v+0.000104*v2VO₂ max=VO₂/percent max

In the above formulas, t is the time to complete a race-level effort inminutes, and v is the speed during the race in meters per minute. Oxygenuptake may be estimated during an athletic effort in substep 6152, usingthe above formula or any other suitable method. VO₂ max may similarly beestimated in substep 6166. The system may also estimate the speed, heartrate, or other parameter corresponding to the level of effort at whichVO₂ max is reached. If desired, time and speed data may have beenentered by the athlete as personal data, or may be measured by the MPN.

In substep 6158, the system may estimate energy consumed during anathletic effort. Energy consumption may be expressed in calories, andmay be estimated based on age, gender, height, and weight, which may beentered as personal data. It may also be estimated based on type ofactivity, HR, speed, elevation gain, and other factors that may bemeasured during an athletic effort. Similarly, the power exerted whileexercising may be estimated in substep 6160.

Lactate threshold (LT) may be estimated in substep 6164. LT representsthe highest level at which exercise may be maintained for an extendedperiod without a build-up of lactate in the blood. It may be measured,for example as a percent of VO₂ max or a percent of MHR above whichlactic acid begins to accumulate in the blood. It may be estimated, forexample, by using the average heart rate for a maximal athletic effortover a half hour. Alternatively, it may be estimated by measuring heartrate during a series of progressively more difficult efforts, and basedon the rate of increase of heart rate between the efforts.

In step 6170, the estimated secondary parameter may be used to modify anathletic workout. For example, the intensity of a workout may beexpressed as percent of LT, and during the workout the system maymeasure heart rate, estimate LT, and increase or decrease the speedsetting of a piece of exercise equipment to maintain the proper level ofeffort. In step 6175, the user may be prompted to modify the level ofeffort based on an estimate of a secondary performance parameter. Forexample, the intensity of a workout may be expressed as percent of VO₂max, and during the workout the system may measure heart rate, estimateVO₂, and prompt the user to speed up or slow down to maintain the properlevel of effort. The estimated secondary parameter may also be displayedfor the user by the MPN, or it may be uploaded to a base station orpersonal computer to be stored, displayed, or analyzed.

FIG. 62 shows illustrative MPN 6200 that may be used to measure aprimary performance parameter and estimate a secondary performanceparameter. INC 6210 may be a control unit or other INC with memory andprocessing capabilities, and may include software to control the otherINCs, as well as to perform the estimation. It may also include memoryto hold software, as well as downloaded personal data such as age,gender, and weight. It may also include a communications device todownload the personal data. INC 6220 may be a display INC, on which theprimary and secondary performance parameters may be displayed. INC 6230may be a heart rate sensor, used for monitoring the athlete's heartrate, which may be a primary performance parameter. INC 6240 may be anaccelerometer for measuring cadence, which may also be a primaryperformance parameter. INC 6250 may be an audio output INC, which may beused to prompt the user to modify the level of effort based on theestimated secondary performance parameter. These INCs are merelyillustrative, and all INCs are optional.

FIG. 63 shows illustrative display screen 6300 that may be displayed bythe athlete's personal computer to allow the entry of personal data. Itmay include entry region 6310 for entering the athlete's name. It mayinclude entry region 6320 for entering the athlete's age. It may includeentry region 6330 for entering the athlete's weight. It may includeselection 6340 for entering the athlete's gender. It may include entryregion 6350 for entering the athlete's height. It may include entryregion 6360 for entering the athlete's RHR. It may include entry region6370 for entering the athlete's MHR. These fields are merelyillustrative. Any suitable personal data may be entered on a screen suchas display screen 6300. Display screen 6300 may also include menu bar6380, which may allow the user to perform other functions. Otherfunctions supported may include file-related functions (e.g., loadingand storing personal data), device-related functions (e.g., downloadingpersonal data to a device), system-related functions, user-relatedfunctions, security-related functions, and help-related functions. Thesefunctions are merely illustrative.

FIGS. 64A through 64F show illustrative display screens that may bedisplayed by a display INC in an MPN during an athletic effort. FIG. 64Ashows screen 6410, which may be a prompt for the athlete to go faster,and may be based on an estimated secondary performance parameter. FIG.64B shows screen 6420, which may display the athlete's currentlymeasured heart rate 6422, percent of MHR 6424, and percent of HRR 6426.FIG. 64C shows screen 6430, which may display the estimated VO₂ max6432, LT 6434, and MHR 6436 at the end of a testing effort. FIG. 64Dshows screen 6440, which may display the athlete's estimated VO₂ duringor after an effort. FIG. 64E shows screen 6450, which may display theathlete's cumulative energy consumption for a workout 6452 and currentpower exertion 6454. FIG. 64F shows screen 6460, which may show theathlete's current actual percent of HRR 6462, the target HRR range forthe workout 6464, and a prompt to the athlete 6466 to modify the levelof effort based on those values.

As described herein, the MPN may be used to collect data, such as heartrate and other athletic data. However, at times the data collection maybe unreliable, for example because of interference with the wirelesscommunications between INCs in the MPN. Temporary interference may becommon because of nearby electro-mechanical devices, other radiofrequency transmitters, poor contact between a metabolic sensor and theskin, and even static electricity between the athlete's body andclothing. One way of handling this is by including memory in the datacollection INC, and retransmitting any lost data once the interferenceis gone. However, this may not be practical, as it may significantlyincrease the cost of the data collection INC. Also, at times datasamples may not be collected successfully by the data collection INC,due to such factors as intermittent connections between the INC and theathlete's body. Therefore, the MPN may include algorithms to recognizeinvalid data samples and to estimate new values for the invalid samples.

FIG. 65 shows illustrative MPN 6500 that may be used to collect data andthat may include detection of invalid data and estimation of replacementdata for the invalid data. Control unit 6520 may collect data samplesfrom heart rate monitor 6530 using wireless communication path 6550 andstore the collected heart rate data in memory in control unit 6520.Control unit may display heart rate data on display 6540. Control unit6520 may detect invalid data received from heart rate monitor 6530,perhaps due to a failure in communication path 6550, and may estimatereplacement data to store and to send to display 6540. Collected heartrate data may also be uploaded to personal computer 6510 and storedthere. Personal computer 6510 may recognize invalid samples, and mayestimate replacement data for the invalid data samples. The collectedheart rate data, including any estimated replacement data may bedisplayed on a monitor attached to personal computer 6510. INCs shownare merely illustrative. All INCs are optional.

FIG. 66 shows flow chart 6600 of an illustrative process for estimatingreplacement data for invalid collected data. All steps are optional andmay be performed in any suitable order. In step 6610, data samples, suchas athletic performance data samples, may be collected by an MPN. Thismay be, for example, heart beat data in substep 6612, or heart rate datain substep 6614. Any suitable type of data may be collected.

In step 6620, one or more invalid samples may be recognized. The invalidsamples may be recognized, for example, by a control unit while data isbeing collected or by a personal computer after collected data has beenuploaded. In substep 6621, invalid samples may be recognized on thebasis of missing values. In substep 6622, invalid samples may berecognized on the basis of zero values, i.e., samples with the value ofzero. In substep 6623, invalid samples may be recognized on the basis ofvalues outside a defined range, for example, heart rate data lower thanthe resting heart rate or greater than the maximum heart rate. Insubstep 6624, invalid samples may be recognized on the basis of a rapidchange in values, for examples values that indicate a very significantchange in heart rate in a very short period of time. In substep 6625,invalid samples may be recognized on the basis of values inconsistentwith other data, for example significantly different from samplescollected before and after, or for example heart rate data inconsistentwith collected speed and elevation data.

In step 6630, replacement values may be estimated for the invalidsamples. Replacement values may be interpolated based on valid samplescollected before, after, or both before and after the invalid samples insubstep 6631. Replacement values may be interpolated linearly in substep6632. Replacement values may be interpolated based on the firstderivative of valid samples in substep 6633. Replacement values may beinterpolated linearly based on the first derivative in substep 6634.Replacement data may be interpolated using a quadratic equation insubstep 6636. Replacement data may be interpolated using a polynomialequation in substep 6638, and may match the values and/or derivatives ofvalid samples at the end points of the interpolation range. The data mayalso be estimated based on data collected in previous sessions undersimilar conditions, for example, the rate of change of the data may bemade to match the rate of change of data collected in the similarsession.

In step 6640, the data samples may be listed, for example on personalcomputer 6510 (FIG. 65). In substep 6642, estimated samples may beindicated in the listing. In step 6645, the data samples may be graphed,for example on personal computer 6510. In substep 6647, estimatedsamples ranges may be indicated in the graph. In step 6650, secondarydata may be derived from the collected data. In step 6652, the secondarydata may be listed, for example on personal computer 6510. In substep6654, secondary data values derived from estimated samples may beindicated in the listing. In step 6656, the secondary data may begraphed, for example on personal computer 6510. In substep 6658,secondary data values derived from estimated samples ranges may beindicated in the graph.

FIG. 67 shows an example 6700 of heart beat data that may have beencollected by an MPN. The data may include samples 6705 through 6740. Itmay be seen that each sample is approximately 0.5 seconds after theprevious, with the exception of sample 6725. This sample was collectedalmost three seconds after the previous sample, indicating that sampleswere likely lost. By interpolation, it may be estimated that fivesamples were missed, and the user's heart rate may be estimated at about122 beats per minute during this time by dividing the number of samplesby the time.

FIGS. 68A and 68B illustrate how samples may be estimated to replaceinvalid samples. FIG. 68A shows illustrative heart rate sample data 6800that may have been collected at a regular interval, such as every 15seconds. In this example, heart rate data is increasing at a rate ofeight beats per minute per minute in first sample range 6805. Heart ratedata samples are all zero and are assumed to be invalid in second samplerange 6810. Heart rate data is increasing at a reduced rate of fourbeats per minute per minute in third sample range 6815. Heart rate datasamples are all out of range and are assumed to be invalid in fourthsample range 6820. And heart rate data is decreasing at a rate of onebeat per minute per minute in fifth sample range 6825.

FIG. 68B shows how replacement values may be created for the invalidsamples, creating revised heart rate sample data 6830. Range 6835, whichcorresponds to range 6810 in the original data, has been filled using alinear interpolation between samples collected just prior to and justafter the invalid data in range 6810. Similarly, range 6840, whichcorresponds to range 6820 in the original data, has been filled using alinear interpolation between samples collected just prior to and justafter the invalid data in range 6820.

FIG. 69A shows illustrative display screen 6900, which lists and graphscollected sample heart rate data. Sample data list 6905 may includeestimated samples 6910. Estimated samples may be marked as estimated,for example with an asterisk. The sample data may also be shown in graph6915. Range 6920 of the graph, corresponding to the estimated data, maybe drawn with a different line style to indicate that the samples wereestimated.

FIG. 69B shows illustrative display screen 6950, which lists anddisplays average heart rate data derived from the collected heart ratedata samples. Data list 6955 may include data point 6960 and 6970derived from estimated samples. Estimated data may be marked asestimated, for example with an asterisk. The derived data may also beshown in graph 6965. Values 6960 and 6970 on the graph, corresponding tothe data derived from estimated samples, may be marked, for example withan asterisk, to indicate that data is estimated.

An MPN may also be used to provide an athlete, such as a runner orwalker, with cadence information and stride length information. FIG. 70shows flow chart 7000 of an illustrative process for providing thisinformation. All steps are optional and may be performed in any suitableorder. In step 7010, an accelerometer may be provided as an INC in theMPN. The accelerometer may send acceleration data to a control unit orother INC with storage capabilities at regular intervals. If desired,multiple accelerometers may be used to measure motion by different partsof the body, or components of motion in different directions. In step7020, the accelerometer may be worn by the user. For example, it may beworn on the leg in substep 7022, the foot in substep 7024, the arm insubstep 7026, or the hand in substep 7028. In step 7030, theaccelerometer may be used to measure cadence. For example, a controlunit may collect the data from the accelerometer, and measure thefrequency at which the data reaches its relative maximums and minimums.This may correspond to the rate at which the user is swinging his or herarms or moving his or her legs, which translates directly to cadence.

In step 7040, a position monitor may be provided as an INC in the MPN.The position monitor may be a GPS monitor in substep 7042. The positionmonitor may send position data to a control unit or other component withstorage capabilities at regular intervals. The position monitor may alsobe worn by the user. In step 7050, the position monitor may be used tomeasure the user's speed, which can be calculated as distance traveleddivided by time. In step 7060, stride length may be calculated based onthe speed and cadence of the user. In substep 7062, the stride lengthmay be calculated as speed divided by cadence. If desired, the units ofstride length displayed to the user may be converted to feet, meters, orother appropriate units. If desired, any of speed, cadence, and stridelength may be displayed for the user. FIG. 45G shows an example of howcadence may be displayed on a display INC in the MPN. FIG. 45H shows anexample of how stride length may be displayed on a display INC in theMPN. If desired, any of speed, cadence and stride length may be recordedfor the duration of a session, and uploaded to a personal computer orbase station for storage, display, or analysis. FIG. 44 showsillustrative MPN 4400 that may be used to calculate and display cadenceand stride length.

A significant impact on athletic performance is the loss of certainvaluable consumables by the athlete during a training or competitionevent. For example, as the user continues at a high level of exertion,levels of water, sodium, carbohydrates, and other nutrients willdecrease, and performance will correspondingly decrease. As levelsdecrease further, performance levels will decrease at an even higherrate, until the athlete is no longer able to continue. However, if theathlete consumes too much of any of these consumables, performance willalso suffer, with conditions such as stomach distress and cramping,hyponatremia, and hypernatremia. The MPN can be used to measure theusage or loss of such consumables, and provide the athlete withreminders to take in specific amounts of one or more of them. FIG. 71shows flow chart 7100 of an illustrative process for providingconsumption reminders to an athlete. All steps are optional and may beperformed in any suitable order.

In step 7110, metabolic data may be collected from a user such as anathlete. For example, an INC in an MPN may include a sensor to measure aspecific metabolic value. In substep 7112, heart rate data may becollected. In substep 7114, skin resistance data may be collected. Insubstep 7116, body temperature data may be collected. In substep 7118,blood pressure data may be collected. In step 7120, the loss of aconsumable may be estimated based on the metabolic data. For example,water may be estimated in substep 7122, carbohydrates in substep 7124,and sodium in substep 7126. A rate of loss of each consumable based onlevel of effort indicated by heart rate may be used Skin resistance maybe used to measure the amount of sweat, which translates to water andsodium loss. An increasing body temperature or blood pressure mayindicate a significant loss of water. Need may also be estimated basedon information stored about the athlete, such as weight or gender. Instep 7130, time may be measured since the most recent reminder, and thetime may be used to refine the estimate of lost consumables. In step7140, the MPN may include an INC to measure the amount of consumable,such as energy drink or water, carried by the user. The measured amountmay be reported to the user. Additionally, the measured amount may beused to calculate the amount previously consumed by the user, and may beused to refine the estimate of needed consumables. In step 7150, theuser may be reminded to consume a consumable based on the estimatedloss. In substep 7152, the reminder may be presented when the loss orusage reaches a defined amount. In substep 7154, the user may be told aspecific amount of the consumable to consume. In substep 7156, the usermay be given an audible reminder. In substep 7158, the user may be givena visual reminder.

FIG. 72 shows illustrative MPN 7200 that may be used to provideconsumable reminders to an athlete. INC 7210 may be a control unit,which may include memory for storing input data samples, a processor forestimating consumable loss, and a wireless communications device forreceiving metabolic data and sending reminders to the user. INC 7220 maybe a metabolic data monitor, such as a skin resistance monitor, bodytemperature monitor, or blood pressure monitor. INC 7230 may be an audiooutput INC for providing audible reminders. INC 7240 may be a displayINC for providing visual reminders. INC 7250 may be a device capable ofmeasure the volume of consumable in, for example, a bladder worn by theuser. INC 7260 may be a heart rate monitor. INCs shown are merelyillustrative and are optional in practice.

FIG. 73 shows illustrative display screen 7300 that may be provided ondisplay INC 7240 (FIG. 72). Prompt 7310 may tell the user to consume aspecific amount of consumable, in this case four ounces of sports drink.Information display 7320 may tell the user how much sports drink isremaining Display 7330 may inform the user that a salt pill should betaken in 15 minutes.

An MPN may be used by a swimmer to provide swimming-related information,such as lap counts. This is illustrated in flow chart 7400 of FIG. 74.All steps are optional and may be performed in any suitable order. Instep 7410, the MPN may include a monitor, such as a flow meter, whichmay be worn by the swimmer in a swimming pool. Other examples ofmonitors that may be used include a turbulence meter, or anaccelerometer to measure arm or leg movements. Preferably, the monitorshould provide data with one characteristic while swimming and anothercharacteristic while turning. If desired, multiple monitors may be worn,of the same or different types. In step 7415, the monitor may be used tomeasure a parameter, such as rate of flow of water past the user's body,amount of water turbulence near the user's body, arm movements, or legmovements. In step 7420, a characteristic of the parameter may beevaluated. For example, one characteristic of the flow may be theirregular readings during the turbulence of the turn at the end of thepool, as opposed to the more cyclical readings seen while swimming.Water flow may maintain a fairly constant positive value while swimming,and may vary in rate and direction while turning. Arm or leg movementsmay have different characteristics while swimming various strokes, whilekicking, while turning, or while resting. Arm or leg movements may beregular and cyclical while swimming, and irregular while turning orresting. If desired, multiple characteristics of the measurement may beevaluated to determine which of several strokes is being used. In step7425, transitions between the two values or characteristics may becounted. In step 7430, the count of transitions may be used, to providea lap count. If desired, more than two characteristics of the parametermay be measured. For example, a third characteristic may be seen whilethe swimmer rests at the end of the pool. Also, differentcharacteristics may be seen when the swimmer performs different strokes.For example, a system in which an athlete wears a water flow meter and asingle accelerometer on one wrist can be used to detect the differencebetween swimming the crawl, breaststroke, backstroke, butterfly, andkicking.

In step 7440, the duration of the two or more characteristics may bemeasured, and this measurement may be used to provide a lap time in step7445. If desired, the measured lap time may be compared with a typicallap time in step 7450, and validated that it falls within a normalrange. For example, if two consecutive measured lap times are much lessthan the typical lap time, the user may have paused in the middle of alap. Similarly, the turn time may be measured in step 7460, and may bevalidated in step 7465. Typical lap times and typical turn times may bestandard values, they may be entered by the swimmer, they may bemeasured during a calibration swim, or they may be entered in any othersuitable way. In a calibration swim, for example, the swimmer may swim asmall number of laps of each stroke, while the system measures thecharacteristics of the data collected by the monitor and measures thetypical lap times. Based on the data collected during a swim workout,the system may construct a model of the entire workout, including eachswim, with type of stroke, speed, and distance for each swim, durationof rest periods, and other data. The data from the model may be stored,displayed, graphed, analyzed, or processed in any other suitable manner.

FIG. 75 shows illustrative MPN 7500 that may be used to provide lapswimming information. INC 7510 may combine the functions of a controlunit and a flow meter, and may be configured to be worn attached to theswimsuit. INC 7520 may combine the functions of a display and anaccelerometer and may be configured to be worn on the wrist. INC 7530may be an audio output INC, and may be configured to be worn attached toa goggle strap or swim cap. INC 7540 may be an input INC worn on thefoot, and it may be operated by tapping the end or bottom of the pool.INCs shown are merely illustrative and are optional in practice.

FIG. 76A shows an example of a screen 7600 that may be displayed ondisplay INC 7520 (FIG. 75) to provide distance information to theswimmer. For example, the swimmer may have configured the system withthe length of the pool, and the MPN may convert a lap count into a totaldistance 7605 for display. Screen 7610 of FIG. 76B may be provided ondisplay INC 7520 at the conclusion of a swim. It shows the distance ofthe swim 7612 which may have been derived from the measured lap count.It shows the swim stroke 7615, which may be determined automaticallybased on the characteristic of data measured by input INC 7510 and 7520(FIG. 75). Screen 7610 also includes total swim time 7620, which may bemeasured by the system.

FIG. 77 shows illustrative display screen 7700 which may be shown on amonitor attached to a personal computer, after data has been uploadedfrom INC 7510 (FIG. 75) of the MPN. Date and time of workout 7710 may bedisplayed, and may have been determined automatically by a clockembedded in INC 7510. Distance 7720 may be listed for each swim, alongwith stroke 7722 and time 7724. Rest times 7726 may also be listed. Theuser may be allowed to scroll through more data, using scroll bar 7730.Other functions may be available using menu bar 7740. Other functionsmay include file-related functions (e.g., loading and saving data sets),data-related functions (e.g., viewing different subsets of data, orviewing the data in different formats or units), profile-related data(e.g., defining the length of the pool, typical swim times, etc.),history-related functions (e.g., comparing performance between swimsessions), and help-related functions.

An MPN may be used to provide form or gait feedback to an athlete orother user. Through the use of one or more accelerometers mounted on apart of the body that is moved during a particular activity, the systemmay compare the measured movements with ideal movements, and providefeedback to the user. An example of such a process is shown in flowchart 7800 of FIG. 78. All steps are optional and may be performed inany suitable order. In step 7810, a user may be allowed to wear anaccelerometer, which may be included in an INC of an MPN. It may be wornon a part of the body that is moved, intentionally or unintentionally,during an activity for which the user desired form feedback. Forexample, it may be worn on a foot, leg, hand, arm, or wrist. Any othersuitable part of the body may also be monitored. In step 7815, multipleaccelerometers may be worn by the user. Multiple accelerometers may beworn on a single part of the body, for example to provide validation ofreadings, or to provide readings of different components of motion indifferent directions. Accelerometers may be worn on corresponding partsof the body, on opposite sides, such as opposite arms or legs, forexample to monitor symmetry of motion. Accelerometers may be worn ondifferent parts of the body, such as an arm and a leg, for example tomonitor different motion aspects of an activity.

In step 7820, the user may be allowed to wear the accelerometer oraccelerometers during a training activity. For example, one or moreaccelerometers may be worn while running in substep 7821, walking insubstep 7822, swimming in substep 7823, bicycling in substep 7824,rowing, during a physical therapy activity in substep 7825, or duringany other suitable activity. In step 7830, characteristics of desiredmovements of the monitored part or parts of the body may be stored. Forexample, the characteristics may have been captured by an expert in theactivity wearing one or more accelerometers in the same location orlocations. Alternatively, the characteristics may have been generated bymonitoring multiple users and averaging the results, or by calculatingoptimum characteristics theoretically. If desired, the characteristicsof desired motions may be stored in a personal computer, or they may bedownloaded into memory in an INC of the MPN. If desired, a coach orphysical therapist may wear the accelerometer or accelerometers anddemonstrate the motion, while the MPN captures the characteristics ofthe coach's motions or therapist's motions.

In step 7835, data from the accelerometer or accelerometers may becollected during the training activity. If desired, the collectedaccelerometer data may be uploaded from the MPN into a personalcomputer. In step 7840, the system may compare the collectedaccelerometer data with the stored characteristics of desired motion.This comparison may be performed in the MPN, for example using a controlunit, or it may be performed using a personal computer to which the datawas uploaded. In step 7845, the comparison may be used to evaluate theuser's form during the training activity, for example to determineincorrect aspects of the user's form. For example, while running,incorrect form may include over-striding, under-striding, lifting thefeet too high, crossing the arms excessively in front of the body, orany other suitable type of incorrect form. Feedback on incorrect formmay be provided to the user during the activity in step 7850. This maybe audible feedback, for example using an audio output INC, and may besynthesized voice. The feedback may be visual feedback, for exampleusing a display INC. In step 7855, feedback may be provided to the userafter the training activity has been completed, for example using apersonal computer. The raw data may be collected and uploaded to thepersonal computer, which may provide the comparison to create thefeedback. Alternatively, the comparison may be performed in an INC ofthe MPN, and the results of the comparison may be collected and uploadedto the personal computer. The feedback may be in the form of a chart,table, or graph, it may be displayed or printed, or it may be presentedin any other suitable form. Form feedback data may be combined withother suitable data when displayed, such as time, speed, or percentgrade uphill or downhill. In step 7860, the collected data or the formfeedback may be transmitted to a coach or physical therapist, forexample over a network such as the Internet, and the coach or physicaltherapist may view the data or feedback.

FIG. 79 shows an example of an MPN 7900 that may be used to provide formfeedback based on accelerometer data collected during a trainingactivity. INC 7930 may be a control unit. The control unit may include aprocessor to control the data collection and to perform the formcomparison. It may also include memory to store desired formcharacteristics and collected data. It may also include a wirelesscommunications device for collecting accelerometer data and forproviding form feedback. INC 7920 may be an accelerometer mounted on theleft wrist, for measuring movements of the left arm. INC 7910 may be adisplay INC for providing visual feedback to the user. If desired, adisplay INC and an accelerometer may be combined into a single INC. INC7940 may be an audio output INC, for providing audible form feedback.INCs 7950 may be accelerometers worn on the feet for measuring movementsof the legs and feet. If desired, accelerometers may be worn on any partof the body, and may be combined with any other INC. If desired, anaccelerometer may be worn on a part of the body that is not expected tomove, and the system may use it to detect incorrect motions by that partof the body. INCs shown are merely illustrative and are optional inpractice.

FIGS. 80A through 80C show examples of screens that may be shown ondisplay INC 7910 (FIG. 79) during a training activity such as running orwalking, to provide form feedback to a user. Screen 8010 of FIG. 80A maysuggest that the user shorten his or her stride, if the collected dataindicates a stride length longer than the desired stride length. Screen8020 of FIG. 80B may suggest that the user relax his or her shoulders.Tightly held shoulders may be inferred, for example, based on the rangeof motion measured from the arms. Screen 8030 of FIG. 80C may suggestthat the user run with less bounce, for example if the collected dataindicates too much vertical motion. Any suitable type of feedback may beprovided for any suitable characteristic of the training activity. Anysuitable training activity may be monitored. Feedback may be providedaudibly during the training activity if desired, for example using audiooutput INC 7940 (FIG. 79).

Screen 8100 of FIG. 81 is an illustrative example of a display screenthat may be displayed after a training activity on a personal computer,to provide form feedback on the training activity. The screen may bedisplayed for the user (e.g., athlete or physical therapy patient) ormay be displayed for a coach, physical therapist or other interestedparty. Graph 8110 may include curve 8120 of ideal motions, and curve8130 of actual motions. This type of graph may illustrate the parts ofthe user's motions that vary from the ideal motions. If desired,multiple types of curves may be shown on the same graph. For example,the forward component of the motion may be represented using one curve,and the side-to-side component of the motion may be represented using asecond curve. As another example, motions of both legs or of both armsmay be shown on a single graph, or motions of an arm and a leg may beshown on the same graph. Legend 8140 may illustrate the line styles ofthe various curves. Menu bar 8150 may provide access to variousfunctions, such as file-related functions (e.g., saving or loadingcollected data files or loading a file with a different set of idealcharacteristics), session-related functions (e.g., looking at data fromdifferent training sessions), data-related functions (e.g., looking atdata collected using different accelerometers during a single session),or help-related functions.

An MPN may be used to provide an athletic training journal. FIG. 82shows flow chart 8200 of an illustrative process for providing anathletic training journal. All steps are optional and may be performedin any suitable order. In step 8210, a mobile electronic journal may beprovided, for example as described earlier in connection with FIG. 42.In step 8220, the journal may include an exercise database. For example,the exercise database may include a list of different types ofexercises, and may include characteristics of each, such as caloriesburned per hour at different intensities or muscle groups trained. Theexercise database may also include data on recommended levels, types,and amounts of exercise. In step 8230, the journal may include anutrition database. For example, the nutrition database may include alist of different types of foods, and characteristics of each, such ascalories, amount of fat, carbohydrates, protein, and other nutrients.The nutrition database may also include data on recommended amounts ofvarious types of nutrients. In step 8240, the journal may include acompetition database. The competition database may include lists ofcompetitions of various types of activities, results, times, and otherinformation. In step 8250, the journal may include a personal database.The personal database may include data on the user's own exercise needsor plans, the user's own nutrition needs, the user's own competitionhistory or goals, or other suitable user data. It may include data onthe user's weight, body fat percentage, waist measurement, and othersuitable health measurements. In step 8260, the journal may include anathletic data collection INC. For example, it may include a heart ratemonitor, a blood pressure monitor, a stopwatch, or other INC that may beused to measure athletic performance. In practice, the user may enterjournal entries related to exercise, nutrition, competition, health, andother related items. For example, the user may log foods eaten,exercises performed, competitions entered, and other items of interest.If desired, journal entries may be linked to suitable database entries.The journal may make automatic calculations related to the journal entryand the database, such as calories consumed or burned, nutrition takenin or needed, etc. Journal entries may also be linked to audio or videomedia files, clock data, position data, or other suitable information.

As described in step 3255 of flow chart 3200 of FIG. 32, an MPN may beused to provide physical therapy functions. This is illustrated in moredetail in FIG. 83. All steps are optional and may be performed in anysuitable order. In step 8310, the MPN may be used to measure range ofmotion. For example, a range of motion monitor may be one of the INCs inthe MPN. In step 8320, the MPN may be used to measure gait or do gaitanalysis. For example, the form feedback functions described previouslyin conjunction with FIG. 78 may be used. In step 8330, the MPN may beused to test muscle strength. For example, a muscle-strength tester maybe incorporated into an INC of the MPN. In step 8340, the MPN may beused to measure changes in a user's physical capabilities. This may bedone, for example, using the functions of the mobile electronic journaldescribed in conjunction with FIG. 42. If desired, the mobile electronicjournal used for physical therapy purposes may include a patientdatabase, a treatment database, an insurance database, a diagnosticdatabase, a range of motion sensor, accelerometers to be used for formfeedback, a muscle strength tester, or other appropriate INCs.

As described in step 3215 of flow chart 3200 of FIG. 32, an MPN may beused to provide medical functions. This is illustrated in more detail inFIG. 84. All steps are optional and may be performed in any suitableorder. In step 8410, an INC may be worn or carried by a doctor, patientor nurse, mounted on equipment such as a wheelchair, or implanted,ingested, or injected into a patient. Any suitable method of providing aportable medical INC may be used. In step 8420, an INC of the MPN may beused to measure a metabolic value of a patient. This may include heartrate in substep 8421, blood oxygen level in substep 8422, bodytemperature in substep 8423, skin resistance in substep 8424, breathrate in substep 8425, blood pressure in substep 8426, blood sugar levelin substep 8427, or any other suitable metabolic parameter. In step8430, the MPN may be used to automatically detect a medical problem. Instep 8440, the MPN may control a medical device, such as a treatmentdevice. The medical device may be an INC in the MPN, or an INC in theMPN may send commands to the device. In substep 8445, the MPN maycontrol a syringe pump. In step 8450, the MPN may provide emergencycommunications, such as an alert to emergency medical personnel. In step8460, the MPN may provide storage of medical records. In step 8465, theMPN may provide storage of insurance information. In step 8470, the MPNmay store a medical database, such as a treatment database, diagnosticdatabase, pharmaceutical database, medical instrument database, orhealth alert database. In step 8480, the MPN may provide a medicaljournal.

FIG. 85 shows flow chart 8500 of an illustrative process for using ameasured metabolic parameter to detect a medical problem. All steps areoptional and may be performed in any suitable order. In step 8510, ametabolic parameter of the user may be measured, for example by an INCof the MPN. This may include measuring heart rate in substep 8511, bloodoxygen level in substep 8512, body temperature in substep 8513, skinresistance in substep 8514, breath rate in substep 8515, blood pressurein substep 8516, blood sugar level in substep 8517, or any othersuitable metabolic parameter that may be measured using a portablesystem. In step 8520, the system may use the measured metabolicparameter to estimate a medical problem. Other factors may also be usedto estimate the medical problem, such as information stored about theuser, level and time of exertion, water and other substances consumed,or other suitable data. Estimating a medical problem may includedetecting a medical problem, predicting a medical problem, or estimatingthe likelihood that the medical problem exists or will occur. Forexample, the system may estimate the likelihood that the user isaffected with dehydration in substep 8521, hyponatremia in substep 8522,a heat injury in substep 8523, heat cramps in substep 8524, heatexhaustion in substep 8525, heatstroke in substep 8526, heart attack insubstep 8527, hypoglycemia in substep 8528, hyperglycemia in substep8529, insulin shock, diabetic coma, or any other medical problem.

The system may take an action to address the estimated medical problemin step 8530. For example, a prompt may be provided to the user,visually or audibly, in step 8540. That may include a prompt to drink insubstep 8541, a prompt to consume sodium in substep 8542, a prompt toslow down in substep 8543, a prompt to cease activity in substep 8544, aprompt to eat in substep 8545, a prompt to take insulin in substep 8546,a prompt to take medication in substep 8547, a prompt to seek emergencymedical attention in substep 8548, or any other suitable prompt. Ifdesired, the system may send an alert message in step 8550. For example,a radio frequency message may be sent to emergency medical personnel. Instep 8560, an audible alert may be sounded. If desired, the action mayinclude control of a medical treatment device, such as a portablesyringe pump, an implanted defibrillator, or other suitable device.

FIG. 86 shows more detail of step 8480 (FIG. 84), providing a mobileelectronic medical journal. All steps are optional and may be performedin any suitable order. In step 8610, a mobile electronic journal may beprovided as described earlier with reference to FIG. 42. In step 8620, atreatment database may be provided, which may provide information aboutdifferent types of medical treatments. A diagnostic database may beprovided in step 8625, and may contain information about differentmedical diagnoses. A patient database may be provided in step 8630, andmay include information about patients of a medical provider, such asmedical history, previous diagnoses, previous treatments, family medicalhistory, risk factors, insurance and payment information or othersuitable types of information. In step 8635, a pharmaceutical databasemay be provided, and may include information about various drugs,including indications for use, recommended dosage, side effects,availability, and other suitable drug information. In step 8640, aninsurance database may be provided, and may include information aboutdifferent insurance providers, such as types of policies, paymenthistories, covered expenses, and other suitable information. A medicalinstrument database may be provided in step 8645, and may includeinformation about various medical instruments, their uses, risks, andother related data. A health alert database may be provided in step8650, and may include information about current and recent healthalerts, such as may be issued by public agencies like the Centers forDisease Control. Any journal entry may be linked to one or more elementsfrom one or more of the included databases. Each journal entry may haveone or more linked images or video clips. Medical images such as x-rays,CAT scans, MRIs, bone scans and the like, may also be input and linkedto journal entries. Each journal entry may also have one or more audioclips, such as a doctor's dictation. The dictation may be translatedinto text using voice recognition software if desired. The journal mayinclude a medical diagnostic instrument in step 8660, and a journalentry may be linked to one or more readings from the instrument. Thejournal may include a medical treatment device in step 8670. Any journalentry may be linked to a usage report of the treatment device.

FIG. 87 shows an illustrative block diagram of a mobile electronicmedical journal 8700. Journal 8700 may include processor 8710, whichmay, for example, be in a control unit. Image memory 8712 for holdingimages and other user data and library memory 8714 for holding one ormore databases may also be included in the control unit if desired, andif desired may be the same memory. Digital camera 8720 may be provided.It may be capable of capturing video still images to link to journalentries. If desired it may also be capable of capturing video clips forthe journal entries. Communications device 8730 may be used fordownloading database information and uploading journal entries. Textinput INC 8740, drawing pad/touch screen input 8742, and voice input INC8744 may be provided to allow text, drawing, and voice portions of ajournal entry respectively. If desired, voice input INC 8744 may alsoinclude a voice recognition capability. A device such as a scanner mayalso be included to input medical images. Clock 8750 may be provided totag journal entries with the current time. Medical device 8752 may beincluded to perform a medical function, and may be either a medicaldiagnostic/input device or a medical treatment device. If desired,multiple medical devices may be included. Display 8760 may also beprovided to view journal entries, database information, and other data.If desired, an audio output INC, not shown, may be provided. INCs may beseparate devices, or may be combined in any suitable fashion. All INCsshown are merely illustrative and are optional.

FIG. 88 shows more detail of step 3260 of FIG. 32, providing featuresfor a disabled user. All steps are optional and may be performed in anysuitable order. In step 8810, Braille may be output for a visuallyimpaired user. For example, an INC may include an output device capableof generating Braille characters. In step 8820, audio may be output fora visually impaired user, in addition to or instead of a visual output.This may include speech generation. In step 8830, information may beoutput visually for a hearing impaired user, in addition to or insteadof an audible output. In step 8835, voice input may be translated into avisual input for a hearing impaired user. For example, the MPN mayinclude an audio input INC to accept a voice input that the user wishesto have translated. The system may use voice recognition to provide avisual display, which may be, for example, text or sign language. Instep 8840, voice input may be accepted from a physically impaired user.In step 8850, breath input may be accepted from a physically impaireduser. This may include allowing a user to input commands to the MPN byblowing into a tube. In step 8860, one or more INCs may be configured tobe mounted on a wheelchair or other device used by a disabled user.

As described in step 3265 of FIG. 32, an MPN may be used by a travelerto provide travel-related functions. This is illustrated in more detailin FIG. 89. All steps are optional and may be performed in any suitableorder. In step 8902, the system may provide language translation. It maytranslate from the user's language to a second language, or from asecond language to the user's language. Input may be text or it may bespoken with voice recognition. Output may be text, spoken with speechgeneration, or both. Translation may be based on a local dialect orlocal slang. In step 8904, the system may provide currency conversion.It may convert home currency to travel currency, or travel currency tohome currency. In step 8906, the system may provide time zoneconversion. It may allow the display of time in the local time zone, inthe home time zone, or any other time zone. In step 8910, the MPN maymonitor the user's position, for example using a GPS monitor.Information on the user's position may be provided to the user in step8912. In step 8914, the system may provide guidance to the user based onthe user's location. In step 8916, the system may provide the user withinformation about a geographical region. This may include geographicalinformation, local customs, laws, tipping guidelines, and other suitablelocal information. In step 8920, the system may provide directions to alocal business or attraction, which may be based on the user's location.In step 8922, a discount with a local business may be provided. In step8924, an advertisement for a local business may be provided to the user.In step 8930, information may be provided about local flora and/orfauna. In step 8932, the system may assist the user in identifying localwildlife. In step 8940, the system may allow the user to maintain atravel journal. In step 8950, the system may provide weatherinformation, such as a local weather forecast. In step 8952, the systemmay provide a transit schedule, such as an airline schedule to or from atravel location, local train and bus schedules, and the like. In step8954, the system may provide a local entertainment schedule. In step8956, the system may allow the user to track expenses, for example ineither local or home currency. The system may accept text input in step8960, voice input in step 8962, video input in step 8964, still imageinput in step 8966, sketch pad input in step 8968, or any other suitableform of user input. In step 8970, the system may be customized to aspecific geographical region. For example, prior to a trip, a user mayenter the destination or destinations into a software applicationrunning on a personal computer. Suitable information for the specificregion or regions may be downloaded over a network such as the Internet,and may be downloaded into an INC of the electronic travel journal, suchas a control unit. Suitable information may include local language anddialect translation dictionaries, currency exchange rates, time zoneinformation, information about a location, businesses, customs, laws,geography, wildlife, flora, climate information and weather forecasts,local transit schedules, local entertainment schedules, and any othersuitable local information. If desired, local information may be updatedwhile traveling, for example by connecting one of the INCs to aconnection such as an Internet connection.

FIG. 90 shows a block diagram of illustrative MPN 9000 that may be usedwhile traveling. MPN may include processor 9010, which may, for example,be part of a control unit. Image memory 9012 may be used for storingvideo images and other user inputs. Database memory 9014 may be used tostore downloaded data. Image memory 9012 and database memory 9014 may bethe same memory, and may be part of a control unit. Digital camera 9020may be provided. It may be capable of capturing video still images. Ifdesired it may also be capable of capturing video clips. Communicationsdevice 9030 may be used for downloading data into database memory 9014,and for uploading user data form image memory 9012. Text input INC 9040,drawing pad/touch screen input 9042, and voice input INC 9044 may beprovided to allow text, drawing, and voice input for travel features,respectively. If desired, voice input INC 9044 may also include a voicerecognition capability. Clock 9050 may be provided to tag user entrieswith the current time, and to provide a user time display. GPS monitor9052 may be included to provide location information in support oftravel features. Display 9060 may also be provided to view information.If desired, an audio output INC, not shown, may be provided. INCs may beseparate devices, or may be combined in any suitable fashion.

Step 8940 (FIG. 89), providing a travel journal, is described in moredetail in FIG. 91. All steps are optional and may be performed in anysuitable order. In step 9110, a mobile electronic journal may beprovided, for example as described in conjunction with FIG. 42. Thetravel journal may be configured, for example, as the MPN shown in FIG.90. Any suitable travel database or databases may be included and storedin database memory 9014. For example, a database of local businesses maybe provided in step 9120. A database of local attractions may beprovided in step 9121. A database of local parks may be provided in step9122. A database of local plants may be provided in step 9123. Adatabase of local animals may be provided in step 9124. A database oflocal geology may be provided in step 9125. A database of local customsmay be provided in step 9126. Any other suitable travel data may also beincluded. The database or databases may be downloaded into the databasememory prior to a trip, based on the planned destination ordestinations. If desired, any database may be updated during a trip, forexample using communications device 9030 to connect to a network such asthe Internet. Any journal entry may be allowed to link to one or moredatabase elements from any of the supported databases. The traveljournal may also provide any other suitable travel function orfunctions, such as language translation in step 9130, currencyconversion in step 9132, time zone conversion in step 9134, routeguidance in step 9136, electronic guidebook features (e.g., informationabout local customs, businesses, attractions, etc.) in step 9138,advertisements in step 9140, a discount at a local business in step9142, a local weather forecast in step 9144, transit schedules in step9146, entertainment schedules in step 9148, or expense management instep 9150. If desired, any journal entry may be linked to an elementfrom another travel feature.

Step 8932 (FIG. 89), assisting a user in identifying local wildlife, isdescribed in more detail in FIG. 92. All steps are optional and may beperformed in any suitable order. The MPN may be configured, for example,as shown in FIG. 90. In step 9210, the user may be allowed to capture animage of wildlife, for example using digital camera 9020, and it may bestored in image memory 9012. In step 9220, a library of images ofwildlife may be stored, for example in database memory 9014. The libraryof images may be downloaded into database memory 9014 in step 9222 forexample using communications device 9030. The images downloaded may bespecific to a geographical region in step 9224. In step 9230, thecaptured image may be compared with the images from the library, using,for example, processor 9010. In step 9232, the system may allow the userto assist the search, for example by using a user input INC to narrow alist of potential matches. In step 9234, one or more potential matchesmay be presented to the user, for example using display 9060. In step9240, additional information may be provided for the wildlife in thelibrary. For example, there may be text descriptions, descriptions ofhabitat and habits, sound samples characteristic of the wildlife, etc.In step 9250, the user may be allowed to annotate the captured image.For example, the user may be allowed to add text in substep 9252, voiceor other captured audio in substep 9254, a drawing in substep 9256, orany other suitable type of user annotation. In step 9260, the capturedimage may be automatically annotated. That may include an annotationwith a link to any match or matches from the wildlife library in substep9262, the time the image was captured determined for example using clock9050 in substep 9264, the location at which the image was captured insubstep 9266 determined for example using GPS monitor 9052, or any othersuitable automatic annotation.

FIG. 93 shows more detail of step 3225 of FIG. 32, supporting outdoorenthusiast features with an MPN. All steps are optional and may beperformed in any suitable order. In step 9310, the MPN may providedirectional information. For example, one of the INCs may include acompass. In step 9320, the MPN may provide position information, if forexample one of the INCs contains a position monitor. In step 9330, theMPN may provide elevation information, using an INC that may include anelevation monitor. In step 9340, the MPN may provide route guidance.Guidance may be based on, for example, topographical information, trailmaps, visual landmarks, and other items useful to a hiker, skier,snowshoer, or other outdoor enthusiast. The MPN may also provide weatherrelated information, such as environmental temperature readings in step9350, humidity readings in step 9360, or barometric readings in step9370. Other suitable outdoor features may also be included if desired.

FIG. 94 shows more detail of step 3240 of FIG. 32, providing anidentification function with an MPN. All steps are optional and may beperformed in any suitable order. In step 9410, the MPN may confirm anidentity using a smart card, with an INC that may include a smart cardreader. In step 9415, the MPN may confirm an identity using a personalcode or password, for example if one of the INCs allows numeric or textentry. In step 9420, an identity may be confirmed using biometrics. Thebiometric may be any suitable technique adapted to a portable INC in theMPN, and may include fingerprint analysis in substep 9421, voiceidentification in substep 9422, hand or finger scanning in substep 9423,analysis of typing characteristics in substep 9424, signature analysisin substep 9425, iris scanning in substep 9426, retina scanning insubstep 9427, or facial scanning in substep 9428. If desired, otherphysical characteristics may be used for identification, such asathletic performance data or metabolic data.

In step 9430, exchange of money may be provided based on the confirmedidentity. In step 9440, the identity may be proven to another person. Instep 9445, the identity may be proven to another system, such as anotherMPN. In step 9450, a product discount may be provided based on theconfirmed identity. In step 9455, product purchasing may be providedbased on the confirmed identity. If desired, the system may storepurchasing information, such as a credit card number, a bank accountnumber, a bank balance, or any other suitable information. If desired,the personal identification may also be used to prevent unauthorized useof the MPN or any of its INCs. The personal identification may also beused to provide secure access to restricted areas, features, and thelike.

FIG. 95 shows more detail of step 3245 of FIG. 32, providing a personalsecurity function with an MPN. All steps are optional and may beperformed in any suitable order. In step 9505, the MPN may be capable ofproviding an audible alert, such as a whistle or other alarm. In step9510, the MPN may be configured to provide an alert to public safetypersonnel. For example, an INC may be provided that includes acommunication INC configured to transmit a message to an emergencydispatch facility, a police department, a fire department, or anemergency medical facility. The audible alert or emergency message maybe triggered by a specific user input, or by any other suitable input orlack of input that may arise in the event of a personal or publicemergency. In step 9520, the MPN may store emergency contact informationfor the user, and may be configured to display or otherwise provide thatinformation with suitable authorization. In step 9530, the MPN may beconfigured to store emergency medical information, such as preexistingconditions, allergies, current prescriptions, etc., and may beconfigured to display or otherwise provide that information withsuitable authorization.

FIG. 96 shows more detail of step 3250 of FIG. 32, providing a militaryfunction in an MPN. All steps are optional and may be performed in anysuitable order. For example, individual military members involved inground support may each be equipped with an MPN having suitable INCs andfunctions. The MPN may provide a communications function in step 9610,such as instant message, and voice, data, text, or video communications.The MPN may provide location functions in step 9620, such as providingthe current location using a GPS monitor. The MPN may include guidancefunctions in step 9630. That may include guidance to specific positionin substep 9632, and directional information in substep 9634. The MPNmay provide weather functions in step 9640. This may include barometricreadings in substep 9642, environmental temperature readings in substep9644, humidity readings in substep 9646, or any other suitable weatherfunction.

As described in step 3270 of FIG. 32, an MPN may support multiplefunctions. Some combinations have been described above. For example,providing both athletic and guidance functions was described inconjunction with FIG. 43A. Providing both music and other audio cues wasdescribed in conjunction with step 2960 of FIG. 29.

Another example of an MPN 9700 that may be used for multiple purposes isshown in FIG. 97. MPN 9700 may include INC 9710, configured to be wornon the wrist. INC 9710 may include a display INC, user controls, and amicrophone. MPN 9700 may include INC 9720, configured to be worn on awaistband. INC 9720 may include control unit functions, clock functions,storage of audio and video media, and a GPS monitor. MPN 9700 mayinclude INC 9730, which may be a video/still camera configured to beworn on a waistband. MPN 9700 may include INC 9740, which may be anaudio output INC. MPN 9700 may include INC 9750, which may be a heartrate sensor configured to be worn on the chest. These INCs are merelyillustrative. Any suitable INCs and method of carrying may be used.

FIG. 98 shows flow chart 9800 of an illustrative process for allowingmultiple uses of MPN 9700 (FIG. 97). All steps are optional and may beperformed in any suitable order. In step 9805, the user may be allowedto listen to music. Music may be stored digitally in INC 9720 and sentto INC 9740 to be heard. In step 9810, the user may be allowed tocollect media data. For example, using the microphone in INC 9710 andusing INC 9730, the user may collect audio data in substep 9812, videodata in substep 9814, and still images in substep 9816. In step 9820,the MPN may collect personal data. That may include, for example, heartrate data 9822 collected from INC 9750 or other suitable athletic data9826, and speed, location 9824, and elevation data collected from theGPS monitor in INC 9720. In step 9830, the media data may be stored, forexample in memory in INC 9720. In step 9832, the personal data may bestored, for example in memory in INC 9720. In step 9834, a relationshipmay be stored between the media data and the personal data. For example,the personal data may be stored at a regular interval with a time stamp,and the collected media data may use the same time stamp. In step 9840,the MPN may interpret collected media. That may include speechrecognition in substep 9842. The interpreted media may be used tocontrol the functions of the MPN in step 9845, for example controllingthe collection of personal data. Alternatively, the interpreted mediamay be stored as text or in another suitable format. In step 9850, datamay be uploaded, for example to a base station or personal computer.That may include uploading the personal data in substep 9852, the mediadata in substep 9854, and the relationship between them in step 9856. Instep 9860, the uploaded data may be stored. This may include storing thepersonal data in substep 9862, the media data in substep 9864, and therelationship data in substep 9866. In step 9870, the personal data maybe displayed. In step 9872, the media data may be displayed or outputbased on its relationship to the personal data. See the description ofFIGS. 46 and 48 for examples of the display of personal data and therelated media data.

FIG. 99 shows illustrative data structure 9900 that may be used to storepersonal data and their relationships to media data. In this example,personal data samples are stored every second. First sample 9920 hastime stamp 9910 and has no linked media. Second sample 9940 has timestamp 9930, and has related media link 9950. In this case, the medialink is the name of a file containing a still image captured by theuser. The MPN has automatically named the file based on the type ofcontent and date and time of capture. Third sample 9970 with stamp 9960in this example has no linked media.

The ability to easily turn off all INCs in an MPN may be useful toconserve power. It may also be useful to terminate radio frequencytransmission in an environment in which they may cause unwantedinterference, such as on a commercial airliner. One of the commandsreceived by the user input INC may be a turn on command, or a turn offcommand. These may be global commands applying to all INCs in the MPN. Aprocess for handling a global turn on command and a global turn offcommand is shown in FIG. 101A and FIG. 101B. All steps are optional andmay be performed in any suitable order. Flow chart 10100 of FIG. 101Ashows an illustrative process that may be performed by a user input INC,or by an INC such as a control unit that receives commands from a userinput INC. In step 10102, the INC may be in its normal “on” state, inwhich it processes commands and data normally. The INC may check foruser input in step 10104. If no user input is received, the INC mayremain in its normal “on” state and continue with normal functions. Ifuser input is received, the INC may check to see if it is a turn offcommand in step 10106. Any appropriate type of user input may be used,such as a voice input, a key press, etc. If the user input is not a turnoff command, the INC may process the user input normally in step 10108and continue with normal functions. If the user input is a turn offcommand, the INC may check to see if the command is validated in step10110. Validation may consist of a second input, holding the key downfor an extended period, the entry of a personal code, or any othersuitable user validation. If desired, the INC may not requirevalidation. If the turn off command is not validated within a definedperiod of time, the INC may return to its normal “on” state. If the turnoff command is validated, the INC may proceed with the turn offsequence.

In step 10112, the INC may send a turn off command to all of the INCs inthe MPN. This may be a single message that is broadcast to all INCs withthe same network identifier in substep 10114. Alternatively, individualmessages may be sent addressed to each INC in substep 10116. In step10118, the INC may wait for confirmation from each other INC. Ifconfirmation is not received, the INC may resend the turn off command,display an error message, or perform another suitable action. Ifdesired, the wait for confirmation step may be optional. Once allconfirmations have been received, the INC may enter a low power mode, instep 10120. For example, if a processor with a sleep mode is used in theINC, it may enter the sleep mode, and it may configure an interrupt tobe generated when a user input is received.

While in the low power turned off state, the INC may check for userinput, in step 10122. For example, an interrupt may be generated when auser input is received. If no user input is received, the INC may remainin the turned off state. If user input is received, the INC may check tosee if it is a turn on command, in step 10124. If not, the user inputmay be ignored and the INC may remain in the turned off state. If theturn on command is confirmed, the INC may resume its high power mode, instep 10126. Turn on messages may be sent to all components in step10128, either as a single broadcast message or as individually addressedmessages. The INC may resynchronize with the other components in step10130. This may include waiting for acknowledgement from the turn onmessage, resending the turn on message if required, or synchronizingfunctions that may have been in progress prior to the turn off command.In step 10132, normal functioning may resume.

Flow chart 10150 of FIG. 101B shows an illustrative process that may beperformed by an INC that does not receive user input. The INC may startin its normal “on” state, in step 10152. It may be performing its normalfunctions, such as data collection, output, control, storage, or otherfunctions or combination of functions. In step 10154, the INC may checkfor a message, such as a wireless message from another INC in the MPN.This may include checking to see if the message has the correct networkidentifier, component identifier, or other address. If no message isreceived, the INC may continue its normal functions. When a message isreceived, the INC may check to see if it is a turn off message, in step10156. If not, the message may be handled normally, in step 10158, andthe INC may remain in its normal “on” state. When a turn off message isreceived, the INC may acknowledge the message in step 10160. Theacknowledgement may be optional. In step 10162, the INC may stop itsnormal functions. This may include stopping any data collection, output,or control functions. The INC may stop sending any information using itswireless transmitter. Preferably, the INC will retain any storedinformation in memory, including information about any processes thatmay have been underway, and any other information required to laterresume normal functions. In step 10164, the INC may enter a low powermode. For example, if a processor with a sleep mode is used in the INC,it may enter the sleep mode, and it may configure an interrupt to begenerated when a wireless message is received.

While in low power mode, the INC may check for incoming messages, instep 10166. If no message is received, it may remain in low power mode.When a message is received, the INC may check to see if it is a turn onmessage, in step 10168. If the message is not a turn on message, the INCmay ignore it and remain in the low power off state. When the turn onmessage is received, the INC may resume its high power mode in step10170. An optional acknowledgement message may be sent in step 10172.Optionally, the INC may resynchronize with other INCs in the MPN, instep 10174. This may include synchronizing any functions that were inprogress when the power off message was received. In step 10176, the INCmay resume normal functions, and return to its normal “on” state.

Although various embodiments have been described herein in terms of anMPN, many of them are possible without all of the features and aspectsof an MPN. For example, components may be designed specifically for asingle purpose, and may not support dynamic configuration of a wirelessnetwork.

Although our present invention has been described in considerable detailwith reference to certain preferred embodiments thereof, otherembodiments are possible. This includes uses, functions, components, andcombinations thereof that may not be fully described. Therefore, thespirit and scope of the appended claims should not be limited to thedescription of the preferred embodiments contained herein.

What is claimed is:
 1. A personal weather and athletic performancemonitoring system configured to be carried by an individual engaged in afitness activity, the system comprising: an input device configured toreceive position data; a processor configured to determine locationinformation for the fitness activity based on the position data; amemory operatively coupled to the processor and storing computerreadable instructions that, when executed by the processor, cause thesystem to determine weather information based on the locationinformation, and to determine athletic performance information; and adisplay screen configured to display the weather information and theathletic performance information to the individual.
 2. The personalweather and athletic performance monitoring system of claim 1, whereinthe input device is a satellite positioning system receiver configuredto receive the position data during the fitness activity.
 3. Thepersonal weather and athletic performance monitoring system of claim 1,wherein the display screen is configured to display the weatherinformation and the athletic performance information simultaneously. 4.The personal weather and athletic performance monitoring system of claim1, wherein the athletic performance information comprises one of speed,pace, elevation, and heart rate information.
 5. The personal weather andathletic performance monitoring system of claim 1, further comprising asensor operatively coupled with the processor and configured to providesensor data to the processor, wherein the system is configured todetermine the athletic performance information based on the sensor data.6. The personal weather and athletic performance monitoring system ofclaim 1, further comprising a separate sensor carried by the individualduring the fitness activity, the separate sensor configured towirelessly communicate sensor data to the processor, wherein the systemis configured to determine the athletic performance information based onthe sensor data.
 7. The personal weather and athletic performancemonitoring system of claim 1, further comprising one of a heart ratesensor and an accelerometer.
 8. The personal weather and athleticperformance monitoring system of claim 1, wherein the display screen isfurther configured to display the location information as a route mapfor the fitness activity.
 9. The personal weather and athleticperformance monitoring system of claim 1, wherein the memory isconfigured to receive a workout plan downloaded from a web server,wherein the workout plan comprises a route of the fitness activity and aweather forecast for the fitness activity.
 10. The personal weather andathletic performance monitoring system of claim 1, further comprising adatabase configured to store the weather information and the athleticperformance information.
 11. The personal weather and athleticperformance monitoring system of claim 1, wherein the processor isfurther configured to correlate the weather information and the athleticperformance information with the location information.
 12. The personalweather and athletic performance monitoring system of claim 1, whereinthe processor is further configured to modify future workout parametersbased on the weather information and the athletic performanceinformation.
 13. A method of displaying weather information and athleticperformance information to an individual via a portable performancemonitoring device configured to be carried by the individual during afitness activity, the method comprising: receiving position data at theportable performance monitoring device; the portable performancemonitoring device determining location information for the fitnessactivity based on the position data; the portable performance monitoringdevice determining the weather information based on the locationinformation; the portable performance monitoring device determining theathletic performance information; and displaying the weather informationand the athletic performance information on a touch screen display ofthe portable performance monitoring device.
 14. The method of claim 13,wherein the position data comprises position data received from asatellite positioning system receiver of the portable performancemonitoring device.
 15. The method of claim 13, wherein the position datacomprises position data of a planned route for the fitness activity. 16.The method of claim 13, wherein the weather information comprisesforecasted weather information for a future specified time correspondingto the fitness activity.
 17. The method of claim 13, wherein the weatherinformation is displayed before the individual engages in the fitnessactivity.
 18. The method of claim 13, wherein the weather informationand the athletic performance information are displayed to the individualwhile the individual engages in the fitness activity.
 19. The method ofclaim 13, wherein the position data comprises position data of a routetraversed by the individual while engaged in the fitness activity. 20.The method of claim 13, wherein the fitness activity comprises one ofrunning, walking, biking, hiking, and skiing.
 21. The method of claim13, wherein the weather information comprises one of environmentaltemperature, humidity, and barometric readings.
 22. The method of claim13, wherein the weather information and the athletic performanceinformation are displayed to the individual after the individualcompletes the fitness activity.
 23. The method of claim 13, wherein theweather information is displayed simultaneously with the athleticperformance information.
 24. The method of claim 13, wherein theportable performance monitoring device determines the athleticperformance information based on data from the portable performancemonitoring device.
 25. The method of claim 13, wherein the portableperformance monitoring device determines the athletic performanceinformation based on data wirelessly communicated to the portableperformance monitoring device from a separate sensor carried by theindividual during the fitness activity.
 26. A method of displayingweather information and athletic performance information to anindividual via a portable performance monitoring device configured to becarried by the individual during a fitness activity, the methodcomprising: receiving position data at the portable performancemonitoring device, wherein the position data comprises position data ofa planned route for the fitness activity; the portable performancemonitoring device determining location information for the fitnessactivity based on the position data; the portable performance monitoringdevice determining the weather information based on the locationinformation, wherein the weather information comprises forecastedweather information for a future specified time corresponding to thefitness activity; the portable performance monitoring device determiningthe athletic performance information; and displaying the weatherinformation and the athletic performance information on a touch screendisplay of the portable performance monitoring device.